core: Beta 0.114 All OZW devices report unavailable untill used
The problem
When I reboot homeassistant all z-wave devices are unavailable and unusable untill I manually use the device or it reports some information in case it is a sensor. So for a switch I have to manually turn device on or off to make it available again. Sensors become available again when they send an update.
When I force a reboot of the (external) OZW container everything is available when OZW has finished loading. I noticed this on the dev builds too, but since that is development that can happen. I tried the several dev builds again to see when it stopped working for me and that is 0.114.0-dev20200724. So 0.114.0-dev20200723 does work as expected. My production system (Home Assistant OS) which runs 113.3 kept working without any problem and keeps receiving all the information. After updating this to the latest beta the same problem occured as on my test system (Home Assistant Container).
I have around 81 devices z-waves in my network.
Environment
| arch | x86_64 |
|---|---|
| chassis | vm |
| dev | false |
| docker | true |
| docker_version | 19.03.5 |
| hassio | true |
| host_os | HassOS 3.13 |
| installation_type | Home Assistant OS |
| os_name | Linux |
| os_version | 4.19.115 |
| python_version | 3.8.3 |
| supervisor | 229 |
| version | 0.114.0b2 |
| virtualenv | false |
- Home Assistant Core release with the issue: 0.114.0-dev20200724 and 0.114.0.b2
- Last working Home Assistant Core release (if known): 0.113.3 and 0.114.0-dev20200723
- Operating environment (OS/Container/Supervised/Core): Home Assistant OS and Container
- Integration causing this issue: OZW
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/ozw
Problem-relevant configuration.yaml
Traceback/Error logs
No errors reported
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 42 (19 by maintainers)
Ok so I have some good news I guess. I can’t reproduce it either when using the asked configuration. Just to make sure I have activated most of the battery devices, only missing 7 which aren’t easy to reach. So it doesn’t seem to be a global issue.
Still not sure what the problem on my side is though… and if other people will have a problem when using external docker applications.
I checked the functionality again from my production system (0.114.0b4) against the HA mqtt test connected to the seperate OZW container. This does work with the mqtt dump automation disabled. So changing mqtt server causes the problem somehow.
Attached two mqtt dumps from the mosquitto_sub command (30 seconds) After a HA reboot, when not all devices are available: mqtt_failing.log After running the mqtt dump from HA to force all device to become available: mqtt_working.log
It’s no problem. I’m glad I can help with the issue. I’m running everything on a Vmware server, so it’s no big issue. I have already setup the new supervisor installation and when I import my configuration the problem is there again. So that stays the same. I have setup the mqtt part already, but to move the ozw installation I need to make some time for that. I have to move the usb stick to the new installation and that creates some downtime. I will see if I can do that this evening or else tomorrow morning.
Note: I edited @MartinHjelmare to request log both from the good and bad version.