I just got my RaZberry, but it does not work
If you see in the log on of these lines:
- Opened device: /dev/ttyAMA0 (or other port)
- Worker thread successfully created
- Worker thread entry point
- Adding job: Get controller info and supported function classes
- SENDING: ( 01 03 00 07 FB )
- Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
- SENDING: ( 01 03 00 07 FB )
- Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
- SENDING: ( 01 03 00 07 FB )
- Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
- Job 0x07 (Get controller info and supported function classes) dropped: too many resends
- Job 0x07 (Get controller info and supported function classes): fail
- Get Serial API Capabilities returned zero.
- Removing job: Get controller info and supported function classes
- Worker thread exit point
- Worker thread successfully finished
- Notification: critical (z-wave): Can not start Z-Wave binding: Error: Bad data - communication failed
First make sure the LED goes on for 1 second on RaZberry board power on. If not, the board is defective. If it goes on, but then flickers or stay on for long time, the board was damaged. (RaZberry based on 3rd generation chip do not do this self test and does not turn on LED at all). Hope you have a working RaZberry board and the problem is not in the hardware.
Then power cycle your box (not just reboot, but unplug power for few seconds!)
Did not helped? Your Raspberry Pi does not see RaZberry on ttyAMA0. Two possible reasons:
- Wrong pins: RaZberry should be installed as on the image in the manual (like shown on the front page of this site).
- Configuration of ttyAMA0 went wrong during installation. Check /etc/inittab and /boot/cmdline.txt to have all mentions of ttyAMA0 commented
I just got my RaZberry, but it does not work
If you see in the log on of these lines:
- No controller device found
- SETDATA controller.data.nodeId = 255 (0x000000ff)
- SETDATA controller.data.homeId = -1 (0xffffffff)
You got one of 3rd generation RaZberry that skipped one minor production step. We apologize, that happens from time to time. But hopefully this is easy to solve. Just do in terminal of your Raspberry Pi:
echo -ne "\x01\x04\x00\x42\x01\xB8" > /dev/ttyAMA0
Then power cycle your box (not just reboot, but unplug power for few seconds!)
This will solve the problem.
RaZberry can include and exclude devices, but they are all marked as dead immediately
If you your homeId is 0x55555555 and you see in the log:
- SETDATA controller.data.homeId = 1431655765 (0x55555555)
You got one of 5rd generation RaZberry that was powered off during self-test process. We apologize, that happens from time to time too. But hopefully this is easy to solve.
http://IP:8083/JS/Run/var t = [ 0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,
0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,
0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF ];
for (var i = 0; i < 1000; i++) { zway.NVMExtWriteLongBuffer(i * t.length, t); }
(this is a link with JS code inside — paste full line in the browser URL bar!)
After this wait for 30 seconds and power off your razberry and power it up again. It will keep lights on for some time (about 5-40 seconds) and go off. After this your homeId will be not 55555555 and Z-Way will be able to include devices and control them.
My devices do not report status to RaZberry if operated locally
With some devices you might notice that they update status if requested in Expert UI, but do not if operated locally. This means your device do not send unsolicited reports to RaZberry. There might be several reasons for this:
- You need to add RaZberry in special Association group dedicated for unsolicited reports. In Z-Wave Plus devices it is first group called Life Line. In older devices it is usually third group (in Fibaro and Z-Wave.Me devices).
- Your device does not allow unsolicited reports to controller. This is certainly due to Lutron patent. All old Duwi devices, some GE and others are like this. As a workaround these devices allows to send Set commands on local operations, so one can trap them in controller and bind to reports. This is a clear hack and is not needed anymore in modern devices.
