Closed foxy82 closed 3 years ago
Hey there @cgarwood, @marcelveldt, @martinhjelmare, mind taking a look at this issue as its been labeled with an integration (ozw
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
This was previously reported in #38658, but ended up being closed for some reason that I didn't understand.
It was closed since it seemed to be a specific mqtt server problem.
I'm seeing this issue with the standard MQTT add-on. I'm using the supervised image in a Proxmox VM.
The versions affected as of today are: HA: 0.117.4, MQTT add-on: 5.1, Supervisor: 2020.11.0, HassOS: 4.15
The MQTT dump call does appear to solve the issue when it happens, but is very much a work-around.
Very good workaround for this issue is to just set up an automation that dumps ozw on boot:
- alias: 'Fix OZW on startup'
trigger:
platform: homeassistant
event: start
action:
- service: mqtt.dump
data:
topic: 'OpenZWave/#'
duration: 5
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
Sometimes when I restart Home Assistant the OZW integration devices remain unavailable. To fix this I have to go into Deverloper Tools -> Service and call mqtt.dump with the following settings
Then all the OZW components instantly become available.
Environment
Problem-relevant
configuration.yaml
N/A mqtt integration and ozw integration are configured using the UI.
I am using the mqtt addon as my mqtt broker.
Traceback/Error logs
Not much in the logs at all:
Additional information