HomeGenie Forum
General Category => Troubleshooting and Support => Topic started by: emerich on November 26, 2015, 08:11:32 AM
-
Hello,
yesterday I upgraded my Raspberry to Version 503 and tried to include my z-wave devices
(Aeon Labs Multisensor Gen5 AEOEZW074, Fibaro Motionsensor FIB_FGMS-001 and Düwi Switch IP20 DUW_064374) They all worked with previous Homegenie 1.0. At first I couldn't include them into the network, but with several retries and changing the timing to 500ms two of them have been recognized
I couldn't get the Fibaro to work.
When I do a query the AEON Labs and the DÜWI are recognized but I can't set any parameters as I get the well known Timeout all the time.
To verify my HW I installed the zwave.me application and did en exclude and include of the devices and all of them worked fine. To avoid interference at the serial connection I killed the relevant tasks and went back to Homegenie with the same result as before. At first I tried to use the devices which I connected via the zwave.me application and I found them as Modules in Homegenie, but also no chance to set parameters. Then I excluded the modules with Homegenie (successful after several retries) and tried to include them again with Homegenie. The result stays the same as described at the beginning.
Any suggestions? The only difference of my installation is mono 4.
br. Christian
-
Please post HG log.
g.
-
Hi Gene,
thanks for fast reply. Find enclosed the logfile.
After restart of the service I saw the zwave switch and I could put him on or of on the widget, but without action on the hardware. Then I tried to do some queries and to get some parameters. For the test I left away the x10 HW. So you might find some x10 errors.
br. Christian
-
Hi Christian,
I see that all packets are very fragmented. Is the serialport used by some other software?
Can you try the patched ZWaveLib and see if it solves the issue? This patch is not about handling fragmented packets, but perhaps it will get some better.
I will think of some other solution for the packet fragmentation issue, though I never seen this behavior before.
http://www.homegenie.it/forum/index.php?topic=1217.msg7645#msg7645 (http://www.homegenie.it/forum/index.php?topic=1217.msg7645#msg7645)
g.
-
Well... I did implement also packet fragmentation handling, so it should work even in that case.
I'm attacching the fixed library if you can test.
- stop hg
- copy ZWaveLib.dll to homegenie/lib/mig folder
- start hg
Cheers,
g.
-
Sorry, but for me nothing changed. No parameter seting or reading!
-
sorry emerich there's an error in the new code:
2015-11-26 18:26:39.8696 Error System.ArgumentException: length
at System.Array.Copy (System.Array sourceArray, Int32 sourceIndex, System.Array destinationArray, Int32 destinationIndex, Int32 length) <0x74e583a0 + 0x00430> in <filename unknown>:0
at ZWaveLib.ZWaveController.ParseSerialData (System.Byte[] message) <0x70564fd8 + 0x002c7> in <filename unknown>:0
at ZWaveLib.ZWaveController.SerialPort_MessageReceived (System.Object sender, SerialPortLib.MessageReceivedEventArgs args) <0x70564f78 + 0x0002b> in <filename unknown>:0
at SerialPortLib.SerialPortInput.OnMessageReceived (SerialPortLib.MessageReceivedEventArgs args) <0x70564ee0 + 0x0006f> in <filename unknown>:0
at SerialPortLib.SerialPortInput.ReaderTask () <0x70e05ee0 + 0x0012f> in <filename unknown>:0
I'll post the fix in a few minutes.
g.
-
Here the fix.
g.
EDIT:
never mind... I need some more time :)
-
Hopefully this will work. Please delete old log file so you can attach only the new debug.
g.
-
To not create confusion attacching ZWaveLib in different threads, I uploaded latest testing release here:
https://sourceforge.net/projects/homegenie/files/testing/
g.
-
Hi Gene,
sorry for the delay and thanks for your effort.
I now had tine to test your latest z-wave library.
Now the query works for all of the devices, but when I try to set some parameters it's running into timeout.
In the logfile I saw that the device sleeping flag is always set and the message will be resent. But most of the tries the device was awake! And one of the sensor nodes realy got the commands, but only one. Never the less all get commands faild with timeout, even when the device was awake. If the device send date on his own they are received. The device Nr.15 is detected during query, but afterwards all communication fails.
I add the log.
If you have some time left, can you please have a look?
Thanks Christian
-
Hi emerich,
I had a look at the logs. Node 15 is implementing the Security Command Class. So I guess the problem is due to the fact that HG implementation of Security Command class has not been verified and so it might be buggy. I've no device implementing that class, so I can't do much about this.
The user that contributed to the security class in HG is snagytx:
https://github.com/genielabs/HomeGenie/pulls?q=is%3Apr+author%3Asnagytx+is%3Aclosed
Hopefully him or some other user having a device implementing the security command class, can help fixing the code.
Cheers,
g.
-
Hi Gene,
thanks for your effort.
br. Christian
-
Hi Gene,
I did a clean install of OS and your application. I also used your new zwave library.
Now I have the sensor witch uses the secure mechanism (AEON Labs gen5 Module18 in the log) included and get the data from it.
On the other side I Included the Fibaro Eye (Module 19) twice but can't get any data (I think because of wrong Group settings). But I can't change the settings.
For both sensors I can't set any parameter. I always get a timeout regardless of the configured timeout value.
The log says that the module is flaged as sleeping even when I wake up the device manualy. I can't see an entry in the log stating that the system gets a message when I wake up the device or clears the sleeping flag.
Any suggestions on that?
Thanks and best regards
Christian
-
How far is the device from the controller? Perhaps it's a radio range problem?
What happen if you position the device closer to the controller?
g.
-
Hi Gene,
I had both sensors about 50 cm away from the raspberry with the attached razberry.
The interesting thing is that with the razberry software I have no problems to set parameter. Also the detection of the status (sleeping or awake) works. Unfortunately it's also not working if I include everything with the razberry software, set all parameters and then switch to the homegenie application.
br. Christian
-
Hi Gene,
I had both sensors about 50 cm away from the raspberry with the attached razberry.
The interesting thing is that with the razberry software I have no problems to set parameter. Also the detection of the status (sleeping or awake) works. Unfortunately it's also not working if I include everything with the razberry software, set all parameters and then switch to the homegenie application.
br. Christian
I emerich,
the problem is that I don't see any "WakeUp" message from any node in your log. Can you try removing the node from z-way and try re-adding them with hg?
g.
-
One more thing, try deleting ZWaveLib cached infos. These are stored in a file called zwavenodes.xml in the homegenie/lib/mig folder.
- stop hg
- delete the zwavenodes.xml file
- start hg
this will make HG query again all data from nodes (so it might take a little more time when doing discovery).
g.
-
Hi Gene,
stopt HG, deleted the xml file, started hg again, made a query. increased the command timeout, made an other query.
During the queries I tried to wake up the motion sensors(18,19) several times.
After that I excluded sensor 19 and reincluded it as sensor 20!
After a new query I saw that the parameters for node 20 have been loaded, but when I tried the setup for the modul 20 the parameters where missing. So I did a query again and finaly got the right sensor name.
Tried to receive the group parameter --> timeout.
Woke up the sensor (3 clicks, constant blue light) and tried to receive the parameter again --> timeout
br. Christian
-
Hi,
I restarted the hg and could get and set parameters for node 20 when I woke up the device. For about 5 min.
Then it fell back to the previous behavour. Timeout on any command even when the sensor is awake.
Maybe hg had for a short time the sleeping flag cleared.
br. Christian
-
What do you mean by increasing timeout? If you refer to the "Command Delay" parameter, please keep it set to 100ms. This parameter will be removed in next HG release.
Anyway I still don't see any wake up message from node 20, though I can see that the discovery was completed succesfully and all data was gathered from the node.
So the only thing I can think of now is comparing Z-Way logs with HG logs.
Expecially when you press the button for waking up the node manually, since there is not trace of that in HG logs.
Cheers,
g.
-
Hi,
I did a short review of the logfile, and saw that I get wake up notifikations from sensor 20 whenever the status is sent. I had the parameter for the wakeup intervall at 10 seconds and everything worked. Wakeup notification every 10 seconds. When I set that back to 7200s the old behavour came back. From the sensor 18 I see also those status messages from the sensor, but no wakeup notification. For the sensor 20 I see those wakeup notifications only when the sensor is transmitting data, but not when I switch it manualy to wakeup state.
It seems that as long as sensor 20 sends data every 10 seconds the sleeping flag is false and commands are sent.
Switching to longer intervals will set the sleeping flag and timeouts happen. Do you know how long messages are stored and wait for the next wakeup?
br. Christian
-
"sleeping" messages are stored forever until succesfully send.
g.
-
Hi,
last time for today!
When I wake up node 20 I get the following messages in hg
"2015-11-28 22:21:49.1471 Debug 20 NodeInfo 04 20 01 30 84 85 80 8F 56 72 86 70 8E 31 9C"
but no message "wake up notifikation" Therefor I think hg doesn't treat this message as wakeup info.
Have to dig a littlebit deeper into zwave protocol to understand the meening of this message.
br. Christian
-
I added wake up on nodeinfo. Please test the library I uploaded here:
https://sourceforge.net/projects/homegenie/files/testing/
g.
-
;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
Hi Gene,
My two sensors are now working quite good!
I now can set all the parameters after waking up the device manualy.
Great Job! Thanks for your time!
br. Christian