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

Discussions about RaZberry - Z-Wave board for Raspberry computer
Post Reply
surdy
Posts: 4
Joined: 29 Apr 2020 04:45

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

Post by surdy »

Just received my Razberry 2 and connected it to my Raspberry pi 3B+ . I mounted it to the Pi and wrote https://razberry.z-wave.me/z-way-server ... ry.img.zip to an SD card and booted it up.

The module LEDs bink when the pi boots. I'm unsure if its supposed to blink afterwards or not but mine did not.

I was able to create an account using find.zwave.me and the login to the UI using <ip>:8083. First thing I tried was to set the timezone using the expert UI but got an error

Code: Select all

 Z-Wave Expert UI - ERROR
Unable to update data.
ssh-ed into the pi and saw the error

Code: Select all

[2020-04-29 02:54:18.509] [I] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2020-04-29 02:54:18.526] [I] [core] Error: Bad data - communication failed
[2020-04-29 02:54:18.527] [I] [core] Tried 5 times without success. Stopping tries.
[2020-04-29 02:54:18.530] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed
I googled around and found instructions to disable Bluetooth. Apparently the official image I flashed had `pi3-miniuart-bt` set on `/boot/config.txt` instead of `pi3-disable-bt`. So I changed that and disabled `hciuart.service`. It did not resolve the issue. I rebooted for good measure but it did not help.


Next I flashed my SD card with latest raspbian stretch image and then used the install script to install Zway

Code: Select all

wget -q -O - https://storage.z-wave.me/RaspbianInstall | sudo bash
After the installation completed I was happy to see that `dtoverlay=pi3-disable-bt` was set on `/boot/config.txt` and `hciuart.service` was disabled.

Hoping for better results I created my admin account and logged in again. But I saw the same results as before `Cannot start Z-Wave binding: Error: Bad data - communication failed`

Code: Select all

pi@raspberrypi:~ $ cat /boot/config.txt 
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
dtoverlay=pi3-disable-bt

Code: Select all

pi@raspberrypi:~ $ systemctl status hciuart 
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

Code: Select all

pi@raspberrypi:~ $ ls -l /dev/ttyAMA0 
crw-rw---- 1 root dialout 204, 64 Apr 29 02:54 /dev/ttyAMA0

enbemokel
Posts: 343
Joined: 08 Aug 2016 17:36

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

Post by enbemokel »

Hi, had an equel problem last time when my SD card died. 2 weeks ago, but with backup a 1 hour issue ;-)
Check the App "zwave network Acces" and see if the ttyAMA0 is correctly inserted, if yes, then just save again. Or stop the app and start again.
Also, restart the raspberry between the different steps, it often is very helpful in case of problems.

surdy
Posts: 4
Joined: 29 Apr 2020 04:45

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

Post by surdy »

Thanks for your response. I tried what you suggested. I get "Something went wrong" error when I try to save the configuration on Zwave Network Access.

Zway server logs still have

Code: Select all

[2020-04-29 19:51:23.765] [I] [zway] Adding job: Get controller info and supported function classes
[2020-04-29 19:51:23.775] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2020-04-29 19:51:23.977] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2020-04-29 19:51:23.977] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2020-04-29 19:51:24.179] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2020-04-29 19:51:24.179] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2020-04-29 19:51:24.381] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2020-04-29 19:51:24.381] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
[2020-04-29 19:51:24.381] [D] [zway] Job 0x07 (Get controller info and supported function classes): fail
[2020-04-29 19:51:24.381] [C] [zway] Get Serial API Capabilities returned zero.
[2020-04-29 19:51:24.381] [I] [zway] Removing job: Get controller info and supported function classes
[2020-04-29 19:51:24.392] [D] [zway] Worker thread exit point
[2020-04-29 19:51:24.392] [D] [zway] Worker thread successfully finished
[2020-04-29 19:51:24.403] [I] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2020-04-29 19:51:24.433] [I] [core] Error: Bad data - communication failed
[2020-04-29 19:51:24.434] [I] [core] Tried 5 times without success. Stopping tries.
[2020-04-29 19:51:24.435] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed
I also found https://z-wave.me/support/hardware-problems/ . I followed the recommendations there as well.
I turned off the Pi and then started it back up
The Zwave module does bling for 1 second on boot and does not stay on for long time
Checked that the module was connected to pins 1-10
I checked /etc/inittab and /boot/cmdline.txt. `/etc/inittab ` does not exist, `/boot/cmdline.txt.` does not have any mention of ttyAMA0

User avatar
PoltoS
Posts: 5534
Joined: 26 Jan 2011 19:36

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

Post by PoltoS »

As a simple check please shortcut TX and RX on the Pi pinout and see if Z-Way will complain in a different way (SOF received instead of ACK). This will test that the port is configured - may be your RaZberry is damaged.

surdy
Posts: 4
Joined: 29 Apr 2020 04:45

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

Post by surdy »

Just to make sure i understood this correctly. You are suggesting remove the module and I short TX(pin 8)and RX (pin 10) on my raspberry pi and then check what I see in z-way server logs ?

User avatar
PoltoS
Posts: 5534
Joined: 26 Jan 2011 19:36

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

Post by PoltoS »

Correct.

If you will see same log, the the port is not configured. If you will see other logs (received packet equal to the sent one), then the port is ok, but the RaZberry is faulty

surdy
Posts: 4
Joined: 29 Apr 2020 04:45

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

Post by surdy »

Thanks for your help PoltoS. I could not find my jumper wires to test what you were suggesting and kind of lost interest in debugging it further. I decided to return my RazBerry and go with another solution instead.

Post Reply