Cannot start Z-Wave binding: Error: Bad data - communication

[oriharel]

Tried both on Raspberry Pi 2 and 3. I always get this error:

(on pi 3 I'm using the latest Pixel os version)

Code: Select all

[2017-01-03 23:26:03.977] [D] [zway] Opened device: /dev/ttyAMA0
[2017-01-03 23:26:03.977] [D] [zway] Worker thread successfully created
[2017-01-03 23:26:03.977] [D] [zway] Worker thread entry point
[2017-01-03 23:26:03.977] [I] [zway] Adding job: Get controller info and supported function classes
[2017-01-03 23:26:03.987] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2017-01-03 23:26:04.190] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2017-01-03 23:26:04.191] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2017-01-03 23:26:04.394] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2017-01-03 23:26:04.395] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2017-01-03 23:26:04.598] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2017-01-03 23:26:04.598] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
[2017-01-03 23:26:04.598] [D] [zway] Job 0x07 (Get controller info and supported function classes): fail
[2017-01-03 23:26:04.598] [C] [zway] Get Serial API Capabilities returned zero.
[2017-01-03 23:26:04.598] [I] [zway] Removing job: Get controller info and supported function classes
[2017-01-03 23:26:04.608] [D] [zway] Worker thread exit point
[2017-01-03 23:26:04.609] [D] [zway] Worker thread successfully finished
[2017-01-03 23:26:04.610] [E] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2017-01-03 23:26:04.631] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed

I checked the 'Known Problems' section:
1. the led is blinking for a second on boot.
2. I removed console=serial0,115200 from my cmdline.txt (I still have console=tty1 in there).

Here is my cmdline.txt:

Code: Select all

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Here is the end of my config.txt:

Code: Select all

# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
config_hdmi_boost=4
overscan_left=24
overscan_right=24
overscan_top=16
overscan_bottom=16
disable_overscan=0
gpu_mem=160
dtoverlay=pi3-disable-bt
enable_uart=1

3. I checked on the "Z-Wave Network Access" app that "Serial port to Z-Wave dongle" is set on "/dev/ttyAMA0".
4. I also tried to change it to "/dev/serial0", "/dev/serial1" and "/dev/ttyS0". all with the same result.
5. also checked that I placed the board on the far right side of the pin array, like shown in the site.

Nothing helps. I understand this is the most common problem with RaZberry. is there anything I can do??

Please help, being troubleshooting this for the last 3 days, emailing the "Support - Z-Wave Europe GmbH" but there answers are not helping.

Thanks.

[JimC]

I am having the same symptoms and have gone through most of the same debugging steps you have. I've added my logs, etc to another post https://forum.z-wave.me/viewtopic.php?f ... =10#p66138 on 30 Dec. Also emailed on 31 Dec but haven't had a reply. I still have the following questions:
1) When I see " [zway] Opened device: /dev/ttyAMA0" in the log does this mean that there is a valid serial device? Guess I'll try booting the system with the Razberry removed and see if there is an error.
2) How can I be sure that /dev/ttyAMA0 isn't still pointing to the Bluetooth device?
3) Is there any simple test (besides the LED's flashing on power up) that would test to see if the board is functional?

[oriharel]

So apparently I do have a problem with the board. I have the 2 leds on all the time. they are on, but in a low brightness. maybe you have the same issue?
could you paste your cmdline.txt content? (/boot/cmdline.txt)

[JimC]

Both my lights are off except for a 1 sec flash on powerup.
My /boot/cmdline.txt is:

Code: Select all

dwc_otg.lpm_enable=0  console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles

[PoltoS]

Make sure there are no other programs using the /dev/ttyAMA0.

You might want to try the image from our site. It has a pre-configured Raspbian.

[JimC]

Just to update, based on my reported symptoms, tech support has asked me to return my board for replacement.