Zwave_JS error 202 Failed to call service, unknown error #106827
Comments
Polosaz
changed the title
|
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zwave_js documentation |
|
I have the same issue and seems to get worse over time. All my lightbulbs and outlers do not respond anymore. Sensors like PIR and door and window swi'tches do report starus but dont operate as they should. I did a renew of the zwave network but this did not help |
|
Please, is there any solution for this? causes great inconvenience |
|
@raman325 - Saw you had quite a few commits around the ZWave 11->12 upgrade timing - anything you can possibly / add or assist with here? This issue(s?) has been persisting for many for 3+ months now - thank you! |
|
I've also been getting intermittent issues for a few months now with errors in the HA logs like: Unable to set value 43-37-2-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202) |
|
Is there a resolution for this? I have the same issue with all my light switches failing to toggle. |
Personally I purchased a Hubitat hub, switched all my Zigbee / ZWave devices over to that, installed the HACS Hubitat<->HA integration and haven't looked back. Maybe this issue(s?) gets resolved in the future, but I wasn't willing to wait so bit the bullet and spent the $150 to go the Hubitat route. |
|
the controller is dropping messages and can't get a message to send successfully, hence the error. I would open an issue in |
|
What worked for me is to restart the zwave UI add on. I'm going to see how
long this works.
Amitabh
…On Mon, Feb 12, 2024, 5:57 PM Raman Gupta ***@***.***> wrote:
the controller is dropping messages and can't get a message to send
successfully, hence the error. I would open an issue in
zwave-js/node-zwave-js as if there is a problem, it would be in the
upstream project. But I would also take a look at the controller statistics
(you can look at the disabled entities or you can expand it from collapsed
on the z-wave configuration panel) and see if you are seeing high volumes
of drops. If you are, then there may be an issue at the RF level, either
caused by interference or hitting range limits
—
Reply to this email directly, view it on GitHub
<#106827 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJJNPXAZ5SBQQ5MDJBWVKDYTKT5DAVCNFSM6AAAAABBJGEGIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZHAYTGNJSHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Same issue with ZWAVE JS UI 3.4.0 on raspberry Pi 5 after upgrading from "V12 dev" to official V12 and core to 2024.2.4. No issue detected before these two upgrades. Work again a few minutes after changing something in configuration (log to file, etc..) but fails after a few minutes. |
|
I have the same issue. I think it happened after upgrading to HA OS 11. When switching a button from the UI manually it takes a second or two then it throws the above mentioned error message in the lower left corner of the screen, but the light still comes on. I also have the feeling that it only happens the first time I try after a while sitting idle. After the error was displayed, and I try a couple more times it does not happen. The most annoying problem is that lights do not come on (or off) when being switched from an automation. It seems to be certain switches only. I have 6, 2 are affected (and used in automations) the others not. Please fix this. It is going on since 5 months now. |
|
There is a fix coming this month. You can check the topic where it is mentioned controller jammed. I believe the root causes is the same but i may be wrong though. The firmware of the zwave stick will be revised . This is relaxed to series 700 stick. Not sure if it solves your issue though.. |
|
@otterlo can you comment more on this fix or the topic where it's referenced? |
|
Hi, it was posted on the SL page, but unfortunately they did not keep their promise and frustration is only increasing. see the lasts posts at the end |
|
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. |
issue-triage-workflows
bot
closed this as not planned
The problem
Since some update of HA Core or Zwave JS integration (not sure exactly which), my HA has failed to call service to Z-wave devices.
I can fix it by rebooting HA but only temporarily. It seems that Zwave devices receive status information (consumption...), but do not respond, or do so erratically, when a service is requested (on/off, light dimming, etc... ). This is not solved by upgrading to HA Core. 12.4
What version of Home Assistant Core has the issue?
core-2023.12.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
No response
Diagnostics information
zwave_js-76a9dabe053b1357644d23961110dbee-Flush Dimmer Plus-945d2800cbdf61812099e45e1b747353.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2024-01-01 18:33:23.073 ERROR (MainThread) [homeassistant.components.zwave_js] Unable to set value 11-38-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202) 2024-01-01 18:33:23.073 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140624394010688] 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 2067, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2104, 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 878, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service await light.async_turn_on(**filter_turn_on_params(light, params)) File "/usr/src/homeassistant/homeassistant/components/zwave_js/light.py", line 304, in async_turn_on await self._async_set_brightness(kwargs.get(ATTR_BRIGHTNESS), transition) File "/usr/src/homeassistant/homeassistant/components/zwave_js/light.py", line 362, in _async_set_brightness await self._async_set_value( 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-01 18:33:32.043 INFO (MainThread) [homeassistant.components.zwave_js] Enabling zwave-js-server logging 2024-01-01 18:33:32.043 WARNING (MainThread) [homeassistant.components.zwave_js] Server logging is set to LogLevel.INFO and is currently less verbose than library logging, setting server log level to DEBUG to match 2024-01-01 18:33:32.044 DEBUG (MainThread) [zwave_js_server] Publishing message: {'command': 'driver.update_log_config', 'config': {'level': 'debug'}, 'messageId': '6e59be05224c48c694b61a382030a8d5'}Additional information
No response
The text was updated successfully, but these errors were encountered: