Hi, Gene.
When I debug HG on my RaspberryPi I often shut down the service by stopping debugging or using Ctrl+C command in terminal.
After this kind of program termination on the next run I often see how Z-Wave Discovery stucks on the first node. Here is a part of log illustrating the issue:
[20:16:58.595540] SPO < 01 04 00 41 01 BB
[20:16:58.615755] SPI > 06 01 09 01 41 93 16 00 02 02 01 32
[20:16:58.621728] SPO < 06
...
[20:17:03.908522] SPO < 01 04 00 41 01 BB
[20:17:03.938434] SPI > 06 01 09 01 41 93 16 00 02 02 01 32
[20:17:03.943991] SPO < 06
...
[20:17:09.219951] SPO < 01 04 00 41 01 BB
[20:17:09.263925] SPI > 06 01 09 01 41 93 16 00 02 02 01 32
[20:17:09.269605] SPO < 06
...
[20:17:14.531722] SPO < 01 04 00 41 01 BB
[20:17:14.585841] SPI > 06 01 09 01 41 93 16 00 02 02 01 32
[20:17:14.591499] SPO < 06
...
[20:17:19.843851] SPO < 01 04 00 41 01 BB
[20:17:19.861429] SPI > 06 01 09 01 41 93 16 00 02 02 01 32
[20:17:19.866814] SPO < 06
While it tries to get NodeProtocolInfo of the first node service can't send or receive any z-wave message.
After stopping and starting the service again it begin to work normally (but sometimes I've to turn it off and on a couple of times).
Do you have any idea what's happening and how to improve stability of the Z-Wave subsystem?
