Z-wave switch not updating state

[Gene]

hi maxflax,

so try waking them up and see what happen. HG should be able to retrieve the node info and then you won't see those errors anymore.

g.

[Gene]

also if you want a switch to be updated when you locally act on it, you have to configure automatic status report on your device.
this is done by changing some variables from the setup page. the configuration variables may vary from brand to brand, so consult your dev docs.

g.

[Gene]

this is an example settings for having an AEON multilevel switch report its status and watt metering.

g.

[maxflax]

This has been working before that hg checked the device status when the device woke up. Which happens when you pressed the button on the device.

Screenshots of the devices not working.

The one reporting as a lampsocket isn't, it's a power switch.

As you can see there isn't much to setup for making it report. Reporting back it's state would in my eyes be a very important feature always turned on. If not having it reporting back would make the device as useless as the telldus.

[Gene]

This has been working before that hg checked the device status when the device woke up. Which happens when you pressed the button on the device.

Screenshots of the devices not working.

The one reporting as a lampsocket isn't, it's a power switch.

As you can see there isn't much to setup for making it report. Reporting back it's state would in my eyes be a very important feature always turned on. If not having it reporting back would make the device as useless as the telldus.

for node 25 you have to set association of group 1 to node 1 (enter number 1 in the association panel and click set, then click get to ensure it is associated to node 1).

node 24 is not supporting Association class, so I don't see any way to make it report status rather than activate polling or having the wake-up program in hg poll its status.

so from what I can understand, all of those issues are just a matter of configuration.

g.

[maxflax]

Yes, the wakeup program is the one updating it before so that is what I had in mind for the switches but it's not working.

[maxflax]

For node 25 your solution worked. Now only the switches and don't register wake up

[Gene]

so the wake up program might need a fix. can you paste the log of what happen when you press the local button on the device?
so I can have a look at the wake up program and see how to fix this.

g.

[maxflax]

Well I thinks thats the problem.. nothing happens when I press the button on the device. The logs dont register anything.

[Gene]

So the device does not have this functionality I guess. You might work-around this using the LevelPoll program.

g.

[maxflax]

well, had this working in an earlier version of homgenie and you fixed the wakeup program then.
see http://www.homegenie.it/forum/index.php?topic=181.msg1000#msg1000

[Gene]

but you said that nothing happen in the logs when you press the button? so how can the wake up program know that the device is trying to communicate?

g.

[maxflax]

It's detecting the wrong device from pepper.. I have this http://www.pepper1.net/zwavedb/device/53
but its detected as http://www.pepper1.net/zwavedb/device/57

[maxflax]

yes nothing in the homegenie.log file when pressing the button on the device. This has been working before that it send a wakeup with the exact same device. So nothing is hindering the wakeup comming trough or something.

[Gene]

try associating the node manually by calling the url:

http://hg_address/api/HomeAutomation.ZWave/node_number/Association.Set/1/1

g.