Z-wave switch not updating state

[maxflax]

Running r501 and I noticed that the switch widget doesn't update the state when I manually turn on or off on the device itself.
Had that problem long time ago also and Gene fixed it quickly, seems that that bug has sneaked itself in again.

Is it possible with a quick fix again Gene?

[mvdarend]

I'm also having strange problems with v501, the Multi instance Fibaro RGBW module doesn't seem to be working properly. Sending a command to any of the colour channels seems to be ignored, settig a value with the widget has unexpected (and random?) results.

At first I thought it was due to some changes I made to the Fibaro RGBW module to make it compatible with HomeGenie Plus, but a clean install of v501 gave the same problems. reverting to v500 fixed the problems for me.

[maxflax]

I have the same problem with all my z-wave devices with r501 as it seems. Tested with a fibaro wall switch and the same result that it doesn't trigger a change. Nothing in the log indicating a change either so something in the z-wave lib i presume that came with r501

probably one of these too fixes that are the culprint
- Added configurable command delay and heal network options to ZWave interface
- Fix blocking event propagation. Events are now processed asynchronously (also solves issue #237)

[jshan]

r501 - also having a z-wave issue.  My Ecolink motion sensor does not respond in HG.  I tried some stuff, like adding and removing it but same result.  I notice it also gives a "error response timeout!" and there are errors in the logfile (see example below).  I switched back to r493 and the sensor responds in HG, although there is also an "error response timeout" (which I never noticed before - and no log error entries) if I attempt to query the device, but this does not appear to affect its functionality.  So, works in r493, does not work in r501.

sample error in r501 log:
015-11-21 19:16:58.6018 Debug Node 6               
2015-11-21 19:16:58.7018 Trace [[[ BEGIN REQUEST ]]]               
2015-11-21 19:16:58.7024 Trace WaitAck               
2015-11-21 19:16:58.7024 Trace Sending Message (Node=6    CallbackId=00    Function=RequestNodeInfo    CommandClass=NotSet)      
2015-11-21 19:16:58.7041 Debug 01-04-00-60-06-9D               
2015-11-21 19:16:58.8038 Debug 06-01-04-01-60-01-9B               
2015-11-21 19:16:58.8052 Trace SendDataReady               
2015-11-21 19:16:58.8052 Debug 06               
2015-11-21 19:16:58.9067 Debug 01-06-00-49-81-00-00-31               
2015-11-21 19:16:58.9195 Trace Error               
2015-11-21 19:16:58.9204 Trace [[[ END REQUEST ]]] took 218 ms

[Gene]

Does copying

- homegenie/lib/mig/ZWaveLib.dll
- homegenie/lib/mig/MIG.HomeAutomation.dll

from r500 to r501 solve the issue? (stop hg, copy the file and then restart).

Cheers,
g.

[maxflax]

Tried to replace the dll but didn't work better.

[Gene]

And what if you replace HomeGenie.exe too?
Just trying to locate what changes could have caused the issue. Anyway there's no relevant modification from r500 to r501 so that's really strange.
After upgrading to r501, everything is still working as before on my side.

g.

[maxflax]

Strange, looks like it doesn't work in any version.. tried complete clean installs to the last 1.0 version and lamp status doesn't get back to homegenie when manually operation the lamp. I know the z-wave door sensors work in those version but haven't tried the lamp since i rarely switch them manually. So for how long they have been broken in the code I don't know. They are Eversrping switches and fibaro inwall dimmers.

[maxflax]

My aeon and fibaro door and window sensors works with reporting when doors are opening etc.
So something with those switches and fibaro pucks. They have been working before since I had a issue with them not updating before.. That time it was a fix in the wakeup poll program that fixed the issue.
I see nothing happening in the log when pressing the switches at the devices.

How can I help you debug this Gene?

I have a Aeon Labs S2 z-stick as controller.

[mvdarend]

Sorry, I won't have time to test the '.dll switch' until Friday, I'll let you know then.

(I'm also using an Aeon Labs S2 z-stick as controller, if that helps)

[Gene]

Running r501 and I noticed that the switch widget doesn't update the state when I manually turn on or off on the device itself.
Had that problem long time ago also and Gene fixed it quickly, seems that that bug has sneaked itself in again.

Is it possible with a quick fix again Gene?

please post the log.

g.

[Gene]

r501 - also having a z-wave issue.  My Ecolink motion sensor does not respond in HG.  I tried some stuff, like adding and removing it but same result.  I notice it also gives a "error response timeout!" and there are errors in the logfile (see example below).  I switched back to r493 and the sensor responds in HG, although there is also an "error response timeout" (which I never noticed before - and no log error entries) if I attempt to query the device, but this does not appear to affect its functionality.  So, works in r493, does not work in r501.

sample error in r501 log:
015-11-21 19:16:58.6018 Debug Node 6               
2015-11-21 19:16:58.7018 Trace [[[ BEGIN REQUEST ]]]               
2015-11-21 19:16:58.7024 Trace WaitAck               
2015-11-21 19:16:58.7024 Trace Sending Message (Node=6    CallbackId=00    Function=RequestNodeInfo    CommandClass=NotSet)      
2015-11-21 19:16:58.7041 Debug 01-04-00-60-06-9D               
2015-11-21 19:16:58.8038 Debug 06-01-04-01-60-01-9B               
2015-11-21 19:16:58.8052 Trace SendDataReady               
2015-11-21 19:16:58.8052 Debug 06               
2015-11-21 19:16:58.9067 Debug 01-06-00-49-81-00-00-31               
2015-11-21 19:16:58.9195 Trace Error               
2015-11-21 19:16:58.9204 Trace [[[ END REQUEST ]]] took 218 ms

this is a similar message from Open-ZWave log:

2015-05-25 14:43:30.284 Info, Node001, Sending (Query) message (Callback ID=0x00, Expected Reply=0x49) - Request Node Info (Node=1): 0x01, 0x04, 0x00, 0x60, 0x01, 0x9a
2015-05-25 14:43:30.294 Detail, Node001,   Received: 0x01, 0x04, 0x01, 0x60, 0x01, 0x9b
2015-05-25 14:43:30.295 Detail,
2015-05-25 14:43:30.296 Info, Node001, FUNC_ID_ZW_REQUEST_NODE_INFO Request successful.
2015-05-25 14:43:30.594 Detail, Node001,   Received: 0x01, 0x06, 0x00, 0x49, 0x81, 0x00, 0x00, 0x31
2015-05-25 14:43:30.595 Detail,
2015-05-25 14:43:30.602 Warning, WARNING: FUNC_ID_ZW_APPLICATION_UPDATE: UPDATE_STATE_NODE_INFO_REQ_FAILED received
2015-05-25 14:43:30.603 Info, Node001, QueryStageRetry stage NodeInfo requested stage NodeInfo max 2 retries 0 pending 1

this indicates that the node is not responding.

g.

[maxflax]

Here is my log and I have done a switch toggle at the device and I cant really see if it even registers a error.
Well my device Id is 25.

Where is that Open-ZWave log?

[Gene]

Hi maxflax,

most of your nodes reply with a :

01-06-00-49-81-00-00-31

only the node number 17, 19,  21, 24 and 25 are working.
What are all of those not-working nodes?
If some of these is a sensor did you try waking it up by pushing the button on it? If you added those nodes with some other software, HomeGenie cannot now what kind of nodes are unless you wake them up or remove/add them again with HG.

The log I pasted if from some forum, just googled "open z-wave 0x49, 0x81, 0x00".

g.

[maxflax]

Yes I have a couple of sensor devices which I haven't woken since my reinstall. Did a complete removal and installation of Homegenie and 've been focused for fixing the other devices like the device with id 25 which is a inwall dimmer from fibaro. Also my everspring wall switches.

All this has been working in the past but don't remember when thou.