Node fails to turn on or off

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using Evolve LRM_AS Multilevel Scene Switch load the OpenZWave Test Program 
or use the ZWManager.SetNodeOn or ZWManager.SetNodeOff methods
2. Attempt to power on or off the node

What is the expected output? What do you see instead?
Expected output is the node turns on or off the light

What version of the product are you using? On what operating system?
1.2.919 Windows 8.1

What branch of the code were you using? (if you just followed the
instructions on the source checkout page, then say trunk.. if you checked
out a branch, please let us know what branch it was)
Don't know

Please include the file OZW_Log.txt from your program. Make sure the file
zwcfg*.xml is NOT present.

Please provide any additional information below.
The zwManager.Setallon or the zwManager.Setalloff works just fine

Original issue reported on code.google.com by T3rr0rBy...@gmail.com on 25 Jan 2015 at 8:24

Attachments:

• OZW_Log.txt

[GoogleCodeExporter]

I am not running windows, but looking at your OZW_Log.txt, you don't seem to be 
calling "SetNodeOn", but "SwitchAllOn". The Switchall is unreliable, because 
your device needs to support it too (most likely your doesn't?).

Original comment by uAle...@gmail.com on 25 Jan 2015 at 8:46

[GoogleCodeExporter]

Are you using the ValueIDs to On/Off the device now? If no reply, i will close 
this one in a few days.

Original comment by uAle...@gmail.com on 15 Feb 2015 at 7:00

[GoogleCodeExporter]

Hi I was using setnodeon and set node off earlier versions but with this 
version although I am using the same format but dimmer neither turn on or off 
can you send me an example main cpp file.
Regards

Original comment by uciba...@gmail.com on 19 Feb 2015 at 11:53

[GoogleCodeExporter]

I think this is an actual bug, theoretically set node on/off should set a value 
id from its minimum to maximum, and the value id should set everything 
in-between. I think now that there are two people reporting the same problem 
that a bug in the code has been verified. My question to the developers is does 
switchallon/switchalloff call the same procedures as setnodeon/setnodeoff... 
i'm guessing not.

I'm happy to provide any information I can, just let me know what and how.

Original comment by t3rr0rby...@hobbyware.org on 21 Feb 2015 at 8:06

[GoogleCodeExporter]

Also I have been busy with many things on the go, but I will test out the 
valueid's tomorrow and get back to you. Sorry for the delayed response and 
testing.

Original comment by t3rr0rby...@hobbyware.org on 21 Feb 2015 at 8:10

[GoogleCodeExporter]

This is not a bug. The SetNode[level/on/off] functions are dependent upon the 
device correctly supporting the basic class, but as pointed out many times 
already, it's unreliable and very inflexible. You should be using ValueIDs and 
the SetValue* functions instead as these are the standard way to control a 
device. 

In future versions, I will probably depreciate the setnode* calls as they cause 
to much confusion. 

Original comment by jus...@dynam.ac on 21 Feb 2015 at 7:17

• Changed state: WontFix