HomeGenie Forum
Development => Bug reporting => Topic started by: maxflax on November 22, 2015, 05:47:35 PM
-
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?
-
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.
-
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)
-
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
-
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.
-
Tried to replace the dll but didn't work better.
-
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.
-
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.
-
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.
-
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)
-
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.
-
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.
-
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?
-
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.
-
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.
-
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.
-
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.
-
this is an example settings for having an AEON multilevel switch report its status and watt metering.
g.
-
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.
-
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.
-
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.
-
For node 25 your solution worked. Now only the switches and don't register wake up
-
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.
-
Well I thinks thats the problem.. nothing happens when I press the button on the device. The logs dont register anything.
-
So the device does not have this functionality I guess. You might work-around this using the LevelPoll program.
g.
-
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 (http://www.homegenie.it/forum/index.php?topic=181.msg1000#msg1000)
-
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.
-
It's detecting the wrong device from pepper.. I have this http://www.pepper1.net/zwavedb/device/53 (http://www.pepper1.net/zwavedb/device/53)
but its detected as http://www.pepper1.net/zwavedb/device/57 (http://www.pepper1.net/zwavedb/device/57)
-
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.
-
try associating the node manually by calling the url:
http://hg_address/api/HomeAutomation.ZWave/node_number/Association.Set/1/1
g.
-
The device is working and I can toggle on/off from Homegenie so don't know how associating it again will help.
My thought would be to force it detected as the right device.
-
I've just updated to r503 and the problems with the Fibaro RGBW module seem to have been resolved. :)
-
Hi mvdarend,
if you have some time, please help testing new ZWaveLib so to ensure we all have issues fixed with it :)
https://sourceforge.net/projects/homegenie/files/testing/
Ensure not to have any other ZWaveLib.dll in the main homegenie folder nor in the homegenie/lib folder.
This file must be copied over the one in the homegenie/lib/mig folder.
g.
-
Hi Gene,
I've overwritten the file in homegenie/lib/mig (the other two folders didn't have a ZWaveLib.dll file).
Stopped the HomeGenie service before copying and then restarted, so far all looks OK. The modifications I made earlier for HomeGenie Plus and the Fibaro RGBW also are working well.
I'll keep an eye on it for the next few days.
-
Is there a way to set the device manually to another device since it's detecting wrong from the pepper database?
-
Problem: Z-wave EcoLink motion sensor not updating
Previously, I had migrated from r493 where motion sensor worked, to r501 where I got timeouts and motion sensor was not responsive.
Updated to r503, rPi, Mono 3.2.8, replaced ZWaveLib.dll per Gene's post
Timeouts still occur.
Now as well, HG does not update the sensor widget and it is stuck with the motion indicator (see attached). I also notice some other icons on the r503 widget which I have not see before (bell, Z-1) which were also in r501 but not in r493.
What can I do to debug this? Or what to look for in the log?
-
Had the same with my reeds sensors, turned out I needed to setup them to send back when changed.
Under Associations you have "Add or remove a node in this group" insert 1 and press add.
then check with "Nodes Id in this group" that it is added.
!!If you have more than 1 group Id you may check that your setting this for the right group first!!
-
Thank you for the quick response, Maxflax. I looked around in HG and I don't see Associations or the option to add/remove node in this group. Is this in a file? Could you point me in the right direction? Thanks.
-
Go to groups, then select your device and there underneath the VM Watt there will be a setup button. This will take you to the setup of the device and there you will find the feature if your device is supported.
You will need to put your device in active state since it's battery driven.
-
I appreciate your help with this, but it does not appear that my device has this feature - see setup page attached. I'm open to any other suggestions to try.
-
Have all the z-wave issues been resolved in r505 or r507? I have r505 and unable to get my door and motion sensors working. They don't seem to be in pepper db though. Lots of variables here and I am new to z-wave....
-
My issue is slightly different but the same topic, so I didn't want to start a new thread. None of my Jasco switches are updating state when manually turning a light on and off. I'm not getting trace error messages, mine show complete. Here is from the console from turning a switch on/off, but nothing changed in the GUI. I assume it has to do with CommandClass=NotSet ?
2016-01-09 12:47:16.7486 Debug 01-10-00-49-84-04-0A-04-10-01-25-27-73-70-86-72-77-BB
2016-01-09 12:47:16.7486 Debug ZWaveMessage (RawData=01-10-00-49-84-04-0A-04-10-01-25-27-73-70-86-72-77-BB)
2016-01-09 12:47:16.7486 Debug ZWaveMessage (Direction=Inbound, Header=SOF, NodeId=0, Type=Request, Function=ApplicationUpdate, CommandClass=NotSet)
2016-01-09 12:47:16.7486 Debug 06
2016-01-09 12:47:16.7507 Debug NodeUpdated (NodeId=4, Parameter=NodeInfo, Value=04 10 01 25 27 73 70 86 72 77)
2016-01-09 12:47:16.7518 Info HomeAutomation.ZWave 4 ZWave Node ZWaveNode.NodeInfo 04 10 01 25 27 73 70 86 72 77
2016-01-09 12:47:16.7518 Trace Complete
2016-01-09 12:47:17.0890 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /hg/html/pages/control/widgets/homegenie/generic/light.js [OPEN]
2016-01-09 12:47:17.0937 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /hg/html/pages/control/widgets/homegenie/generic/light.js [CLOSED AFTER 0.005 seconds]
2016-01-09 12:47:17.1191 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /hg/html/pages/control/widgets/homegenie/generic/light.html [OPEN]
2016-01-09 12:47:17.1222 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /hg/html/pages/control/widgets/homegenie/generic/light.html [CLOSED AFTER 0.003 seconds]
2016-01-09 12:47:18.9295 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [OPEN]
2016-01-09 12:47:18.9313 Info WebServiceGateway 192.168.21.5 HTTP GET 200 /api/HomeAutomation.HomeGenie/Config/Interfaces.List/ [CLOSED AFTER 0.002 seconds]
2016-01-09 12:47:19.5622 Debug 01-10-00-49-84-04-0A-04-10-01-25-27-73-70-86-72-77-BB
2016-01-09 12:47:19.5622 Debug ZWaveMessage (RawData=01-10-00-49-84-04-0A-04-10-01-25-27-73-70-86-72-77-BB)
2016-01-09 12:47:19.5622 Debug ZWaveMessage (Direction=Inbound, Header=SOF, NodeId=0, Type=Request, Function=ApplicationUpdate, CommandClass=NotSet)
2016-01-09 12:47:19.5626 Debug 06
2016-01-09 12:47:19.5626 Debug NodeUpdated (NodeId=4, Parameter=NodeInfo, Value=04 10 01 25 27 73 70 86 72 77)
2016-01-09 12:47:19.5637 Trace Complete
-
Hi All,
The Fibaro Multi-Instance switches are still not working with ZWaveLib 1.0.12. Tested it on a Pi and Windows. They work if manually triggered but not via Smart Lights, etc.
Unfortunately the logs do not give any idea of what's wrong.
Any idea what could still be causing this?