Every now and again a Razberry hangs with this message:
[[19.5240421295166,[3,0,0,0,1,1,1,1,1,1,0],29,"SwitchMultilevel Get","Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Removing job due to too much retransmitions",[29,2,38,2,37]],[19.58403778076172,[3,0,0,0,1,1,1,1,1,1,0],24,"MultiChannel encapsulation","Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Removing job due to too much retransmitions",[24,6,96,13,1,3,49,4,5]],[19.644033432006836,[3,0,0,0,1,1,1,1,1,1,0],7,"MultiChannel encapsulation","Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Removing job due to too much retransmitions",[7,6,96,13,1,3,49,4,5]],[19.704029083251953,[3,0,0,0,1,1,1,1,1,1,0],32,"Meter get (v2)","Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Could not be delivered to Z-Wave stack
Removing job due to too much retransmitions",[32,3,50,1,0,37]],[19.740026473999023
etc, for every message in the queue
Basically, it fails to deliver any messagei
Doing a 'sudo reboot' does not help. Only a power cycle (by removing the USB power) helps.
My questions are:
1. What is this error, and why does it happen every X weeks.
2. Can I recover without unplugging the device from power?
I can fairly easy detect these messages in the queue using your great API, so I know when it goes wrong, but want to take actioni.
'Could not be delivered to Z-Wave stack' - Only power cycle helps
So in a situation now where
So in a situation now where after 'sudo reboot'ing the device does not work (Web GUI won't even come up again, but I can SSH into the raspberry which seems to work just fine, just not the Razberry). Looked in the z-way-server-log and found a list of messages like this:
[2013-09-12 23:58:10.785] 0xf3 ZMERestore
[2013-09-12 23:58:10.785] SETDATA controller.data.capabilities = int[7]
[2013-09-12 23:58:10.786] [00] 1
[2013-09-12 23:58:10.786] [01] 128
[2013-09-12 23:58:10.786] [02] 210
[2013-09-12 23:58:10.786] [03] 240
[2013-09-12 23:58:10.786] [04] 241
[2013-09-12 23:58:10.786] [05] 242
[2013-09-12 23:58:10.787] [06] 243
[2013-09-12 23:58:10.787] ---------------------------
[2013-09-12 23:58:10.787] Job 0x07 (Get controller info and supported function classes): success
[2013-09-12 23:58:10.787] Device is not authorized. Terminating...
[2013-09-12 23:58:10.787] Failed to join worker thread: 35
[2013-09-12 23:58:10.798] Error returned from zway_fc_serial_api_set_timeouts(zway, 10, 10, NULL, NULL, NULL): Function class not supported by the hardware (-4)
[2013-09-12 23:58:10.798] Adding job: WatchDog Start
[2013-09-12 23:58:10.798] Error returned from zway_fc_get_home_id(zway, _zway_discover_on_success_get_home_id, _zway_discover_on_fail_get_home_id, NULL): Function class not supported by the hardware (-4)
[2013-09-12 23:58:10.798] Removing job: Get controller info and supported function classes
[2013-09-12 23:58:10.809] Worker thread exit point
failed to discover ZWay: -9
Z-Way version v1.3.1 from 2013-05-19 23:54:27 +0400 (build e717f1057ab76a00fa02d9e6546e360ad3390f36)
Using default configuration file config.xml
Starting Z-Way for device /dev/ttyAMA0...
[2013-09-12 23:58:10.785] 0xf3 ZMERestore
[2013-09-12 23:58:10.785] SETDATA controller.data.capabilities = int[7]
[2013-09-12 23:58:10.786] [00] 1
[2013-09-12 23:58:10.786] [01] 128
[2013-09-12 23:58:10.786] [02] 210
[2013-09-12 23:58:10.786] [03] 240
[2013-09-12 23:58:10.786] [04] 241
[2013-09-12 23:58:10.786] [05] 242
[2013-09-12 23:58:10.787] [06] 243
[2013-09-12 23:58:10.787] ---------------------------
[2013-09-12 23:58:10.787] Job 0x07 (Get controller info and supported function classes): success
[2013-09-12 23:58:10.787] Device is not authorized. Terminating...
[2013-09-12 23:58:10.787] Failed to join worker thread: 35
[2013-09-12 23:58:10.798] Error returned from zway_fc_serial_api_set_timeouts(zway, 10, 10, NULL, NULL, NULL): Function class not supported by the hardware (-4)
[2013-09-12 23:58:10.798] Adding job: WatchDog Start
[2013-09-12 23:58:10.798] Error returned from zway_fc_get_home_id(zway, _zway_discover_on_success_get_home_id, _zway_discover_on_fail_get_home_id, NULL): Function class not supported by the hardware (-4)
[2013-09-12 23:58:10.798] Removing job: Get controller info and supported function classes
[2013-09-12 23:58:10.809] Worker thread exit point
failed to discover ZWay: -9
Z-Way version v1.3.1 from 2013-05-19 23:54:27 +0400 (build e717f1057ab76a00fa02d9e6546e360ad3390f36)
Using default configuration file config.xml
Starting Z-Way for device /dev/ttyAMA0...
Your RaZberry seems to die...
Your RaZberry seems to die... Can you paste the line with RECEIVED string?
-
- Posts: 9
- Joined: 01 Jun 2013 18:12
Re: 'Could not be delivered to Z-Wave stack' - Only power cy
Hi, i have the same problem since a few days.
how can i check if the razberry card is out of order ?
Thanks,
Christophe
how can i check if the razberry card is out of order ?
Thanks,
Christophe
Re: 'Could not be delivered to Z-Wave stack' - Only power cy
Does it recover after full reboot? Does it work stable/unstable?
-
- Posts: 9
- Joined: 01 Jun 2013 18:12
No ACK received before timeout
This is what it aswers me (in the progress column) whatever the command i try (for example"(Re)include device").
I tried to re-install the software, soft reboot, hard reboot (power off and on) and it's always the same thing. When i try to include a device, the red led shines but no device can be included.
I tried to re-install the software, soft reboot, hard reboot (power off and on) and it's always the same thing. When i try to include a device, the red led shines but no device can be included.