HassOS 4.8+ Razberry breaks on RPI

Installation Home Assistant OS
1

Hi there,

I updated to HassOS 4.8 today and now my ZWave driver seems broken? All entities anavailable & cannot startup network manually. Any idea/help?

Thanks in advance!

ZWave log:
2020-06-02 21:53:28.731 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-02 21:54:13.938 Info, Setting Up Provided Network Key for Secure Communications
2020-06-02 21:54:13.939 Info, mgr, Added driver for controller /dev/ttyAMA0
2020-06-02 21:54:13.939 Info, Opening controller /dev/ttyAMA0
2020-06-02 21:54:13.941 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-06-02 21:54:13.942 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-06-02 21:54:13.943 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 21:54:13.943 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 21:54:13.943 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 21:54:13.943 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 21:54:13.943 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 21:54:13.943 Detail,
2020-06-02 21:54:13.944 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 21:54:13.944 Detail, contrlr, Notification: DriverFailed

1 Like
2

same problem! z-wave broken after update to 4.8!

1 Like
3

Likewise :frowning:

1 Like
4

I also have this problem!

1 Like
5

I very recently had a similar experience, but I’m not sure it was after the upgrade to 4.8. In my case, the USB port for the Z-Wave dongle had changed inexplicably from /dev/ttyACM0 to /dev/ttyACM1. While reading up, I learned how to avoid this from causing service disruption by assigning the dongle using a different syntax, i.e. /dev/serial/by-id/usb-0658_0200-if00. You can find this value by going to Supervisor -> System -> Hardware.

The upgrade to 4.8 may have been blamed because it forces a reboot, but any reboot would have caused the observed behaviour.

1 Like
6

Hello! for usb right, it can be! Razberry connects to the board! and there /dev/ttyAMA0

7

I am so annoyed - I have the same problem practically my whole home automation depends on Z-Wave.
The only thing I have managed to find is https://www.home-assistant.io/docs/z-wave/installation/#first-run I also noticed something not before in the change on the options.xml https://www.home-assistant.io/docs/z-wave/installation/#first-run but this didn’t work. My hardware settings are

serial:

* /dev/ttyAMA0

Configuration YAML

zwave:
  usb_path: /dev/ttyAMA0
  network_key: !secret network_key
  autoheal: false
8

I also have the problem and the situation emerged with the update to 4.8. So it is definitely related. I am not sure how I finally made my zwave running as I mainly use zigbee and zwave only for one sensor, so I did not care but my configuration file did not have any zwave configuration. If it was deleted or the integration worked on some default config, I don’t know.

9

Hi - here’s a question and am tempted to try …did you try and add zwave in via integrations as I was thinking of hashing out the config and adding that way

10

I tried to play with config, no effect. I currently deleted the zwave integration and will try to add it again. I have just one multisensor, so I dont care but I can imagine that if your house is built on zwave, you might be a bit pi** off about this bug

11

I do not think it is a configuration issue. As my ZWave log above shows there is a driver issue… I have also raised this with Pascal Vizelli here:


The issue is marked there as “downstream” - no idea what that means.
Maybe it is a good idea you guys also raise your problems there?

br

12

whoever installed version 4.9? Is the problem gone?

13

I am on Hassio and it hasn’t come available yet

14

Hello,

I have just installed version 4.9 and I still have the problem:

ha os update --version 4.9

2020-06-03 23:34:28.304 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-03 23:34:40.611 Info, Setting Up Provided Network Key for Secure Communications
2020-06-03 23:34:40.612 Info, mgr,     Added driver for controller /dev/ttyAMA0
2020-06-03 23:34:40.612 Info,   Opening controller /dev/ttyAMA0
2020-06-03 23:34:40.612 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-06-03 23:34:40.613 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-06-03 23:34:40.613 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-03 23:34:40.614 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-03 23:34:40.614 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-03 23:34:40.614 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-03 23:34:40.614 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-03 23:34:40.614 Detail,
2020-06-03 23:34:40.614 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-03 23:34:40.614 Detail, contrlr, Notification: DriverFailed

I only have a Z-wave modules, so I’m very annoyed.

15

Same, no improvement with 4.9

2020-06-04 13:51:46.971 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-04 13:52:40.976 Info, Setting Up Provided Network Key for Secure Communications
2020-06-04 13:52:40.977 Info, mgr, Added driver for controller /dev/ttyAMA0
2020-06-04 13:52:40.977 Info, Opening controller /dev/ttyAMA0
2020-06-04 13:52:40.977 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-06-04 13:52:40.978 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-06-04 13:52:40.978 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-04 13:52:40.978 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-04 13:52:40.978 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-04 13:52:40.978 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-04 13:52:40.978 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-04 13:52:40.979 Detail,
2020-06-04 13:52:40.979 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-04 13:52:40.979 Detail, contrlr, Notification: DriverFailed

16

Can you update title of this topic to : “HassOS 4.8+ Razberry breaks on RPI” ?

17

pulsar thank you very mach!!! gave me a thought!!
im run ha os update --version 3.8 and z-wave work again!!!

by the way 4.9 zwave not starting!

18

Can you tell me how to downgrade back to the old HassOS 3.12. My core temperature is too high. It’s now 15 degrees hotter than normal and there is no abatement on the memory being consumed. I know it’s now 4gb for the journal but I have surpassed that I’m sure. Nobody seems to answer me.

19

Just updated it. I raised an issue on Github. Can you second that?

20

Thanks for the tip! I also downgraded:

SSH into your RPI and run

ha os update --version 3.8

ZWave network is currently rebuilding. i hope they fix the new OS soon.

br