hassio-addons/addon-zwave-js-ui

ZWAVE-JS-UI addon frequently dies on version newer than 2.1.2

gburtscher opened this issue · 1 comments

gburtscher commented

Problem/Motivation

The Zwave-JS-UI addon frequently dies on versions newer than 2.1.2. After stopping / starting the Add-On everthing is fine again. This is happing after a few hours. An automation jobs in the night helps a little bit. It´s not very clear on which gaps this is happening.
(it happens twice a day or more). I also tried to enable - save and disable - save the SOFT-RESET within the Zwave-JS-UI Settings (didn´t make any difference).

After the addon died it´s no more possible to switch on/off light. There are messages displayed that the Zwave controller is no longer reachable. Sometimes are 1 or 2 Sensative Guard Strip devices are greyed out (but however they are reachable) ...

(Why the issue was filed)

Should be stable like in version 2.1.2, as we also cannot install new versions of the Homeassistant Core / Addons (because of dependencies)

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce: It is not clear how I can reproduce this.

The used versions are:
Core 2024.1.5
Supervisor 2023.12.1
Operating System 11.4
Frontend 20240104.0

Z-Wave JS UI
Current version: 3.2.1 (Changelog)
zwave-js-ui: 9.7.1
zwave-js: 12.4.1

Hardware:
Rasp PI 4 with HAOS 11.4
RaZberry 7 Pro by Zwave.me FW = 7.38 (should be the newest FW)

Error Message in the HA Core:
(every time I try to switch on / off e.g. Light switches, I got the error messages like below)

2024-01-22 21:27:58.595 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.mobile_app entity: sensor.ipad_waltraud_last_update_trigger
2024-01-22 21:28:28.350 ERROR (MainThread) [homeassistant.components.zwave_js] Unable to set value 22-37-1-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202)
2024-01-22 21:28:28.351 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546292435264]
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 333, in _async_set_value
return await self.info.node.async_set_value(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/node/init.py", line 543, in async_set_value
result = await self.async_send_command(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/node/init.py", line 501, in async_send_command
return result_task.result()
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/client.py", line 130, in async_send_command
return await future
^^^^^^^^^^^^
zwave_js_server.exceptions.FailedZWaveCommand: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 882, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 952, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zwave_js/switch.py", line 90, in async_turn_off
await self._async_set_value(self._target_value, False)
File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 338, in _async_set_value
raise HomeAssistantError from err
homeassistant.exceptions.HomeAssistantError
2024-01-22 21:28:39.735 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:41.479 ERROR (MainThread) [homeassistant.components.zwave_js] Unable to set value 22-37-1-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202)
2024-01-22 21:28:41.480 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546292435264]
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 333, in _async_set_value
return await self.info.node.async_set_value(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/node/init.py", line 543, in async_set_value
result = await self.async_send_command(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/node/init.py", line 501, in async_send_command
return result_task.result()
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/client.py", line 130, in async_send_command
return await future
^^^^^^^^^^^^
zwave_js_server.exceptions.FailedZWaveCommand: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 882, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 952, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zwave_js/switch.py", line 85, in async_turn_on
await self._async_set_value(self._target_value, True)
File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 338, in _async_set_value
raise HomeAssistantError from err
homeassistant.exceptions.HomeAssistantError
2024-01-22 21:28:42.023 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:42.359 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:42.588 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:42.785 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:42.812 WARNING (SyncWorker_15) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.100'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

2024-01-22 21:28:44.716 WARNING (SyncWorker_14) [py.warnings] /usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host '192.168.1.101'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(

Error message in the ZWAVE-JS-UI addon

2024-01-22 21:29:54.310 INFO APP: GET /health/zwave 301 1.678 ms - 191
2024-01-22 21:30:24.446 INFO APP: GET /health/zwave 301 1.680 ms - 191
2024-01-22 21:30:37.975 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-01-22 21:30:42.076 INFO Z-WAVE: Controller status: Controller is Ready
2024-01-22 21:30:42.078 ERROR Z-WAVE-SERVER: Failed to send the command after 5 attempts (ZW0202)
ZWaveError: Failed to send the command after 5 attempts (ZW0202)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:5256:23)
at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:5454:28)
at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:5565:15)
at Proxy.set (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)
at Proxy. (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)
at ZWaveNode.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:1150:39)
at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:19:43)
at Object.node (/opt/node_modules/@zwave-js/server/dist/lib/server.js:42:92)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:125:99)
at WebSocket. (/opt/node_modules/@zwave-js/server/dist/lib/server.js:57:45)

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Restore of old version:

Home Assistant 2023.10.3 Supervisor 2023.12.1 Operating System 11.4 Frontend 20231005.0 - latest
and ZWAVE-JS-UI 2.1.2

Logfile_HA-Core.txt
Logfile_Zwave-JS-UI.txt

Would be great if there is someone with an idea / workaround about this.

thanks a lot
Gerd

github-actions commented

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!