You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since several months I am having the trouble that Z-Wave integration stops to work with "Failed to unload" error. All the time I thought it is about the integration not working, why I also reported this in Error unloading entry Z-Wave JS for zwave_js. Since I thought it is about the integration, I downgraded to 2023.9.3 which didn't help. Error were less, though, but nevertheless, they came.
@kpine has looked into it and in his opinion this has to do with the z-wave js addon and not with the integration. So I am back on 2024.2.2 and error are again more often. This morning it didn't work for more than 20 minutes and than stopped :-(
I have no clue what is causing this issue as I didn't change - at least I am not aware of any intentional change from my side - anything in my setup. I have the same setup since my initial start and it worked for over a year. Since last autumn I have masive trouble with Z-Wave which most of device I have use.
I see in core log is that shortly before the error popped up "something" (Integration) disconnected from server:
2024-02-22 07:46:48.459 INFO (MainThread) [homeassistant.components.zwave_js] Disconnected from server. Reloading integration
2024-02-22 07:46:48.507 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry Z-Wave JS for zwave_js
Z-Wave add on stopped logging 5 minutes earlier after many "unexpected" entries for DRIVER. Does this mean server stoped to work there? This would explain why integration disconnected from it.
But honestly, I have no clue where to start with all this. I looked into open and closed issue of the add on but didn't find anything like the issue I have,
Please, can someone look into this and help me! thx,
Zavjah
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.4.4
Steps to reproduce the issue
Simply use HA with Z-Wave integration and official Z-Wave add on
System Health information
There are currently no repairs available
Anything in the Supervisor logs that might be useful for us?
See attached log file (supervisor_2024-02-22T08-28-23.189Z.log) above
Anything in the add-on logs that might be useful for us?
See attached log file (240222_074100_zwave_2024-02-22.log) above
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
Since several months I am having the trouble that Z-Wave integration stops to work with "Failed to unload" error. All the time I thought it is about the integration not working, why I also reported this in Error unloading entry Z-Wave JS for zwave_js. Since I thought it is about the integration, I downgraded to 2023.9.3 which didn't help. Error were less, though, but nevertheless, they came.
@kpine has looked into it and in his opinion this has to do with the z-wave js addon and not with the integration. So I am back on 2024.2.2 and error are again more often. This morning it didn't work for more than 20 minutes and than stopped :-(
I have no clue what is causing this issue as I didn't change - at least I am not aware of any intentional change from my side - anything in my setup. I have the same setup since my initial start and it worked for over a year. Since last autumn I have masive trouble with Z-Wave which most of device I have use.
Please find here all logs I habe from this morning:
240222_090700_home-assistant_core.log
240222_074100_zwave.log
240222_092800_supervisor.log
I see in core log is that shortly before the error popped up "something" (Integration) disconnected from server:
Z-Wave add on stopped logging 5 minutes earlier after many "unexpected" entries for DRIVER. Does this mean server stoped to work there? This would explain why integration disconnected from it.
But honestly, I have no clue where to start with all this. I looked into open and closed issue of the add on but didn't find anything like the issue I have,
Please, can someone look into this and help me! thx,
Zavjah
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.4.4
Steps to reproduce the issue
Simply use HA with Z-Wave integration and official Z-Wave add on
System Health information
There are currently no repairs available
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
ha core info
arch: aarch64
audio_input: null
audio_output: null
backups_exclude_database: false
boot: true
image: ghcr.io/home-assistant/raspberrypi3-64-homeassistant
ip_address: 172.30.32.1
machine: raspberrypi3-64
port: 8123
ssl: false
update_available: false
version: 2024.2.2
version_latest: 2024.2.2
watchdog: true
ha supervisor info
addons:
name: Terminal & SSH
repository: core
slug: core_ssh
state: started
update_available: false
version: 9.9.0
version_latest: 9.9.0
name: Mosquitto broker
repository: core
slug: core_mosquitto
state: started
update_available: false
version: 6.4.0
version_latest: 6.4.0
name: PS5 MQTT
repository: df2164f9
slug: df2164f9_ps5_mqtt
state: started
update_available: false
version: 1.3.3
version_latest: 1.3.3
name: File editor
repository: core
slug: core_configurator
state: started
update_available: false
version: 5.8.0
version_latest: 5.8.0
name: Z-Wave JS
repository: core
slug: core_zwave_js
state: started
update_available: false
version: 0.4.4
version_latest: 0.4.4
addons_repositories:
slug: local
slug: 00185a40
slug: df2164f9
slug: 5c53de3b
slug: core
slug: a0d7b954
arch: aarch64
auto_update: true
channel: stable
debug: false
debug_block: false
diagnostics: true
healthy: true
ip_address: 172.30.32.2
logging: info
supported: true
timezone: Europe/Berlin
update_available: false
version: 2024.02.0
version_latest: 2024.02.0
wait_boot: 5
The text was updated successfully, but these errors were encountered: