z-wave.me

Sent working version of 4 & not working version of 6 channel.

Is there any example of a TRAIC (or other) hardware solution for Z-UNO, both in Hardware and Sketch?

I have a application where I need to control the Line Voltage 240VAC to 0-240VAC.

Thanks, As HIGH & LOW do not to be defined, that answers the most important question. I couldn't see where lastValue1 == LOW could be used as LOW was not defined, but as it does not need definition you have answered the question. I thought that == was a Boolean expression, have I mistook it for some...

Please refer to the code snippet below that come from the Sensor wall based Switch example. byte lastValue1 = HIGH; byte lastValue2 = HIGH; // the setup routine runs once when you press reset: void setup() { pinMode(BTN_PIN1, INPUT_PULLUP); pinMode(BTN_PIN2, INPUT_PULLUP); } // the loop routine runs...

The INT1 and INT2 must be the problem.

There are different code revisions, each one had different PIN OUTS, the last sketch with published code was an earlier version, since then it has undergone many revisions.

The code works and I'm happy to work forward from here, Next is to design a PCB with onboard power supply (240VAC to 5VDC).

I just read the proposed road map and see some big developments ahead.
User defined Parameter(s) is a big plus for developers and I for one am eager to see it developed.

I checked the following PINOUTS (17 to 23) with all interfering with another Binary Switch (2,3 or 4) Then I changed the PINOUT'S to 8 to 5, the result that the sketch and UI now works as intended. Can anyone explain why there is interference on PINS 17 to 23 or are those PINS reserved for other use...

Now this really starts to get weird. I had initially thought that it might be due to the PINOUTS and had today intended play around with them, but after I plugged the ZUNO into my PC prior to uploading a new sketch I thought I should check the current sketch. What I found was that the UI indication ...

This is the UI when Binary 1 is switched ON. BInary4 indicates ON, but is not actually ON, it only indicates ON.

Perhaps there is some logic that can be added to turn the UI off? Not sure just thinking out aloud?