core: Z-Wave JS Errors & Excessive memory use when Z-Wave JS to MQTT also installed and running
The problem
Entire Home Assistant system becomes unstable with Supervisor crashing and Z-wave nodes failing to boot. It appears after Supervisor 2021.3.0 that the Z-wave JS integration/add-on is utilizing constant processor resources when also running Z-wave JS to MQTT. Zwave JS also shows errors every few seconds. Now on reboots, certain nodes fail to recover from cache on the Zwave controller. What is also noticeable is that processor use is up a consistent 30% after Core-2021.2.3. When Z-wave JS to MQTT is uninstalled, system powered down completely and rebooted, Z-Wave JS runs a normal processory/memory load but fails to recognize any node. Zwave controller is Z-Wave.me UZB.
What is version of Home Assistant Core has the issue?
core-2021.3.1
What was the last working version of Home Assistant Core?
core-2021.2.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS v0.1.10
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Example YAML snippet
# Put your YAML below this line
Anything in the logs that might be useful for us?
# Put your logs below this line
Z-Wave JS Logs
-----------------
21:59:50.254 DRIVER
21:59:50.384 DRIVER serial port errored: Error Resource temporarily unavailable Cannot lock port
Unable to start driver [Error: Error Resource temporarily unavailable Cannot lock port]
[21:59:53] INFO: Successfully send discovery information to Home Assistant.
21:59:57.826 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
21:59:57.853 DRIVER version 6.5.0
21:59:57.855 DRIVER
21:59:57.991 DRIVER serial port errored: Error Resource temporarily unavailable Cannot lock port
Unable to start driver [Error: Error Resource temporarily unavailable Cannot lock port]
[22:00:00] INFO: Successfully send discovery information to Home Assistant.
22:00:04.338 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
22:00:04.365 DRIVER version 6.5.0
22:00:04.368 DRIVER
22:00:04.538 DRIVER serial port errored: Error Resource temporarily unavailable Cannot lock port
Unable to start driver [Error: Error Resource temporarily unavailable Cannot lock port]
[22:00:06] INFO: Successfully send discovery information to Home Assistant.
22:00:08.331 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
22:00:08.354 DRIVER version 6.5.0
22:00:08.355 DRIVER
22:00:08.445 DRIVER serial port errored: Error Resource temporarily unavailable Cannot lock port
Unable to start driver [Error: Error Resource temporarily unavailable Cannot lock port]
[22:00:09] INFO: Successfully send discovery information to Home Assistant.
Core Logs
------------------------
2021-03-04 21:59:34 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.5', 3000)]
2021-03-04 22:00:14 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hall_and_stair_floor_lights_current_value
2021-03-04 22:00:35 WARNING (MainThread) [homeassistant.components.automation.adjust_hall_light_brightness] Adjust Hall Light Brightness: Already running
2021-03-04 22:00:52 WARNING (MainThread) [homeassistant.components.light.reproduce_state] Invalid state specified for light.hall_and_stair_floor_lights_current_value: unavailable
2021-03-04 22:00:59 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.hall_and_stair_floor_lights_current_value
Constant Z-Wave Memory use
Note difference in processor use from before core-2021.3.0 to after.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18 (8 by maintainers)
Fantastic! I’m very happy to hear this! Thank you for the additional information.
The item in the config entry data that controls if the integration should use and control the official add-on is
"use_addon": true.Before core-2021.3.1 the reconfiguration flow didn’t unset this setting. So even if you reconfigured the integration, targeting the same USB controller, and unselected the use add-on checkbox, it would still remember the original setting. This was fixed in core-2021.3.1.
Yes, I saw that and thank you for this information. Isn’t that counterintuitive, to get a warning saying it aborted, but to save the new configuration as you’ve stated?
Since I’m remote now, I can’t do a full hard-power off reboot for the controller. I’ll report back when I get the opportunity. During the last soft reboot, ZwaveJS did not restart, but I’m still missing nodes.