ZHA 194 Status.NWK_INVALID_REQUEST

schwickster commented 6 months ago

The problem

As reported in 106732 I had similar problems where all my Zigbee devices weren't responding (greyed out) and ZHA gave the error 194 Status.NWK_INVALID_REQUEST. After a compleet restart of my Nuc and 10 minutes orso later, the integration restored itself. As requested in 106732 I made a seperate incident. According to @puddly the coordinator is failing to send the startup broadcast with NWK_INVALID_REQUEST, the firmware is probably in a bad state and required a hardware reset to start working again.

Restarting the docker container nor restarting HA resolved the issue. For now it seems it fixed itself but it was a weird issue none of the less.

The conbee 2 stick is using the 0x26780700 firmware that was released in 2022 of May.

logging-zha.zip config_entry-zha-2d4ce5a7029511ebbb3f111d42e919ee.json.txt

What version of Home Assistant Core has the issue?

2023.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

See description

Example YAML snippet

No response

Anything in the logs that might be useful for us?

See attachments

Additional information

Nope

home-assistant[bot] commented 6 months ago

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

zha documentation zha source _{^{(message by IssueLinks)}}

MacGyverr commented 6 months ago

Same issues here, all of my Centralite 3326-L motion detectors stopped working following the .1 update and the .2 didn't fix anything. I have powered HA down then up several times, and made sure the Sonoff_Zigbee_3.0_USB_Dongle_Plus has also been power cycled. The remaining motion detectors all bounce between there and unavavilable, and do seem to work, just with triggers that are delayed and then fire once they come back online. Here it was 20 minutes ago. Here it is now.

The outlet switches still work. When I removed one of the motion detectors and tried to re-add it, it says "Interview Complete, Configuring" but it just keeps running through "NWK" hex numbers. Tries remaining: 1 [0x5E36:1:0x0003] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.CLUSTER_COMMAND: 1>, is_manufacturer_specific=False, direction=<Direction.Server_to_Client: 0>, disable_default_response=0, reserved=0, is_cluster=True, is_general=False), tsn=127, command_id=64, *direction=<Direction.Server_to_Client: 0>) [0x5E36:1:0x0003] Sending request: trigger_effect(effect_id=<EffectIdentifier.Okay: 2>, effect_variant=<EffectVariant.Default: 0>) [0x5e36] Extending timeout for 0x7f request [0x5E36:1:0x0500] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 322, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/zigpy_znp/zigbee/application.py", line 1100, in send_packet raise DeliveryError( zigpy.exceptions.DeliveryError: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

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

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 83, in wrapper with wrap_zigpy_exceptions(): File "/usr/local/lib/python3.11/contextlib.py", line 155, in exit self.gen.throw(typ, value, traceback) File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 75, in wrap_zigpy_exceptions raise HomeAssistantError(message) from exc homeassistant.exceptions.HomeAssistantError: Failed to send request: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

[0x5E36:1:0x0500] Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/zigpy/device.py", line 322, in request await send_request File "/usr/local/lib/python3.11/site-packages/zigpy/application.py", line 833, in request await self.send_packet( File "/usr/local/lib/python3.11/site-packages/zigpy_znp/zigbee/application.py", line 1100, in send_packet raise DeliveryError( zigpy.exceptions.DeliveryError: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

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

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 83, in wrapper with wrap_zigpy_exceptions(): File "/usr/local/lib/python3.11/contextlib.py", line 155, in exit self.gen.throw(typ, value, traceback) File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/init.py", line 75, in wrap_zigpy_exceptions raise HomeAssistantError(message) from exc homeassistant.exceptions.HomeAssistantError: Failed to send request: Request failed after 5 attempts: <Status.NWK_INVALID_REQUEST: 194>

0x5E36: Device seen - marking the device available and resetting counter 0x5E36: Update device availability - device available: True - new availability: True - changed: False [0x7A12](SP 224): Device seen - marking the device available and resetting counter [0x7A12](SP 224): Update device availability - device available: True - new availability: True - changed: False Feeding watchdog 0x85CB: last_seen is 40496628.39032769 seconds ago and ping attempts have been exhausted, marking the device unavailable 0x85CB: Update device availability - device available: False - new availability: False - changed: False Feeding watchdog [0x7A12](SP 224): Device seen - marking the device available and resetting counter [0x7A12](SP 224): Update device availability - device available: True - new availability: True - changed: False Feeding watchdog 0x5E36: Device seen - marking the device available and resetting counter 0x5E36: Update device availability - device available: True - new availability: True - changed: False Feeding watchdog 0x85CB: last_seen is 40496692.392077446 seconds ago and ping attempts have been exhausted, marking the device unavailable 0x85CB: Update device availability - device available: False - new availability: False - changed: False

I can add the full log if it's helpfull.

issue-triage-workflows[bot] commented 3 months ago

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.

home-assistant / core