Page 1 of 1

Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed

Posted: 15 May 2018 11:23
by tallackn
Got a Pi 3B+ with a new RaZberry2 board. Got bluetooth disabled in config.txt to free up /dev/ttyAMA0 for the z-wave-server. All looks great.

Power on the Pi, go see the brief little dual LED on the R2 board so that I know it draws power from the GPIO, system boots, web services come up on http://localhost:8083. Sweet.

But, one pretty big problem. The daemon is not getting any serial responses back from the R2 board. :(

The /var/log/z-way-server.log shows this at the end.

Code: Select all

[2018-05-15 20:10:54.939] [D] [zway] Opened device: /dev/ttyAMA0
[2018-05-15 20:10:54.939] [D] [zway] Worker thread successfully created
[2018-05-15 20:10:54.939] [D] [zway] Worker thread entry point
[2018-05-15 20:10:54.940] [I] [zway] Adding job: Get controller info and supported function classes
[2018-05-15 20:10:54.949] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 20:10:55.151] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 20:10:55.151] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 20:10:55.353] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 20:10:55.353] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 20:10:55.554] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 20:10:55.554] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
[2018-05-15 20:10:55.554] [D] [zway] Job 0x07 (Get controller info and supported function classes): fail
[2018-05-15 20:10:55.554] [C] [zway] Get Serial API Capabilities returned zero.
[2018-05-15 20:10:55.554] [I] [zway] Removing job: Get controller info and supported function classes
[2018-05-15 20:10:55.564] [D] [zway] Worker thread exit point
[2018-05-15 20:10:55.565] [D] [zway] Worker thread successfully finished
[2018-05-15 20:10:55.575] [E] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2018-05-15 20:10:55.593] [I] [core] Error: Bad data - communication failed
[2018-05-15 20:10:55.594] [I] [core] Tried 5 times without success. Stopping tries.
[2018-05-15 20:10:55.596] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed
I'm hoping it is not a faulty RaZberry2 board. How could I tell?

Re: Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed

Posted: 15 May 2018 12:19
by tallackn
Restarting the z-way-server service sometimes produces different results in the /var/log/z-way-server.log where it complains about unknown packet type. I'm really thinking my board is faulty now. :(

Code: Select all

[2018-05-15 21:16:31.440] [D] [zway] Opened device: /dev/ttyAMA0
[2018-05-15 21:16:31.440] [D] [zway] Worker thread successfully created
[2018-05-15 21:16:31.440] [D] [zway] Worker thread entry point
[2018-05-15 21:16:31.441] [I] [zway] Adding job: Get controller info and supported function classes
[2018-05-15 21:16:31.451] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 21:16:31.652] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 21:16:31.652] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 21:16:31.653] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x04
[2018-05-15 21:16:31.653] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x10
[2018-05-15 21:16:31.653] [W] [zway] Received SOF, while awaiting ACK
[2018-05-15 21:16:31.653] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x04
[2018-05-15 21:16:31.653] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x10
[2018-05-15 21:16:31.653] [W] [zway] Received SOF, while awaiting ACK
[2018-05-15 21:16:31.654] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x04
[2018-05-15 21:16:31.654] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x10
[2018-05-15 21:16:31.654] [W] [zway] Received SOF, while awaiting ACK
[2018-05-15 21:16:31.654] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x04
[2018-05-15 21:16:31.654] [E] [zway] RECEIVED UNKNOWN PACKET TYPE: 0x10
[2018-05-15 21:16:31.654] [W] [zway] Received SOF, while awaiting ACK
[2018-05-15 21:16:32.259] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 21:16:32.259] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2018-05-15 21:16:32.461] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2018-05-15 21:16:32.461] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
[2018-05-15 21:16:32.461] [D] [zway] Job 0x07 (Get controller info and supported function classes): fail
[2018-05-15 21:16:32.462] [C] [zway] Get Serial API Capabilities returned zero.
[2018-05-15 21:16:32.462] [I] [zway] Removing job: Get controller info and supported function classes
[2018-05-15 21:16:32.472] [D] [zway] Worker thread exit point
[2018-05-15 21:16:32.472] [D] [zway] Worker thread successfully finished
[2018-05-15 21:16:32.484] [E] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2018-05-15 21:16:32.518] [I] [core] Error: Bad data - communication failed
[2018-05-15 21:16:32.520] [I] [core] Tried 5 times without success. Stopping tries.
[2018-05-15 21:16:32.525] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed

Re: Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed

Posted: 15 May 2018 14:36
by tallackn
Now I have a real suspicion it has something to do with the Pi 3's and the UART performance. Too much noise in google search results to be sure, but enough doubt to think maybe the board is not faulty.

I know for sure nothing else is hooking to /dev/ttyAMA0 because I can see the z-way-servers using it with with lsof as it is talking to the UART.

So I am sure of 2 things:
1: The software is configured correctly and successfully accessing the serial interface.
2: The hardware is put together correctly with a nice high amperage USB power supply and the R2 is plugged correctly into the 1-10 GPIO ports.

:(