Closed trickv closed 9 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!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
@Shulyaka it seems like https://github.com/zigpy/zigpy-xbee/pull/149 is not compatible with all XBee firmwares
@trickv which module and firmware do you have (if you know)?
@trickv We are preparing a fix. As a workaround, if you have access to the file system, in your /usr/local/lib/python3.11/site-packages/zigpy_xbee/zigbee/application.py
, line 195 (at the start of the energy_scan
function), please insert the following line:
return {c: 0 for c in channels}
Example:
async def energy_scan(
self, channels: zigpy.types.Channels, duration_exp: int, count: int
) -> dict[int, float]:
"""Runs an energy detection scan and returns the per-channel scan results."""
return {c: 0 for c in channels}
all_results = {}
for _ in range(count):
results = await self._api._at_command("ED", duration_exp)
...
@trickv which module and firmware do you have (if you know)?
Took me a while, I had to go get XCTU out to figure out the firmware version :) My module is an Xbee S2C with firmware version 4061 which looks to be the latest (https://hub.digi.com/support/products/digi-xbee/digi-xbee-s2c/?path=/support/asset/xbee-zb-s2c-firmware-4061/)
I'll go try that workaround now. Thanks!
@trickv We are preparing a fix. As a workaround, if you have access to the file system, in your
/usr/local/lib/python3.11/site-packages/zigpy_xbee/zigbee/application.py
, line 195 (at the start of theenergy_scan
function), please insert the following line:return {c: 0 for c in channels}
Example:
async def energy_scan( self, channels: zigpy.types.Channels, duration_exp: int, count: int ) -> dict[int, float]: """Runs an energy detection scan and returns the per-channel scan results.""" return {c: 0 for c in channels} all_results = {} for _ in range(count): results = await self._api._at_command("ED", duration_exp) ...
Hacked in-place on my 2023.11.0 container and this workaround does the trick. Thanks!
I'll keep an eye out for your upstream patch to make it into a release and give it a go when it does.
I have the same issue with a conbee II USB dongle I tried downgrading core to 2023.10.5 but zigbee still not working I am running OS so I am not sure I can get to file structure, don't know enough about that. No sure if this log file is helpful home-assistant.log Anything I can try?
I have the same issue with a conbee II USB dongle I tried downgrading core to 2023.10.5 but zigbee still not working I am running OS so I am not sure I can get to file structure, don't know enough about that. No sure if this log file is helpful home-assistant.log Anything I can try?
Hi @zacolly - I'm not a Zigbee expert, but reading your comment and looking at the log file, this isn't the same bug that I hit. Mine was specific to the underlying library that uses an Xbee as my Zigbee coordinator; the Conbee uses a different backend. The patch mentioned here won't fix your issue.
I'd recommend opening a new bug report and specifically mention Conbee in the title to see if anyone else with a Conbee is having trouble.
@zacolly Yeah, that's another issue. TXStatus.MAC_CHANNEL_ACCESS_FAILURE
indicates you have too much interference. Not related to the update.
Make sure to use a USB extension cable for the Conbee, move it away from APs/metal, USB 3 SSDs, ...
Thanks @TheJulianJES Amateur mistake, was reconfiguring my data cabinet devices at the same time as the update and had my HA NUC temporarily shoved out of the way. Now I know why the downgrade didn't work :)
Hi.
I lost all the mnemonics used by my Zigbee devices, I have to find back all the uid (that only HA can understand, but not a human) and reconfigure my scripts. A real nightmare :'(
Maybe did you already had such an issue (it is a real issue, because nothing was working), and a way to convert unreadble uid into human readable is :-) .
Thanks. Dom
I have a similar issue with a digi x stick. But it says "Invalid_Command" instead of "Invalid_Parameter".
I also tried the fix in https://github.com/zigpy/zigpy-xbee/pull/168, but this did not work.
But using return {c: 0 for c in channels}
did the trick and allowed me to start, but it seems like I cannot use any of my zigbee devices and get lots of timeouts.
I just have to find out wether this is because I tried to do a firmware update with xctu or if this is another issue.
Not sure if evrything important is inside the log:
Hi @F4bsi , which firmware do you have?
Hey @Shulyaka, thanks for the help :)
This is what XCTU says:
Its an really old Digi XStick2 ZB (at least thats what it says on the sticker on the stick)
Hey @Shulyaka, thanks for the help :) This is what XCTU says:
Its an really old Digi XStick2 ZB (at least thats what it says on the sticker on the stick)
Hi, I can confirm my XBee2 with the latest Coordinator API firmware (21A7) also has this issue. I have used the recommended manual patch and it is fully working now.
Running home-assistant 2023.12.0b1 which includes zigpy-zbee==0.20.0 and it's working out of the box for me :+1:
The problem
I upgraded to 2023.11.0 today and my ZHA integration has failed to load. When I go back to 2023.10.5 it seems to work. Maybe some quirk with my Xbee coordinator?
What version of Home Assistant Core has the issue?
core-2023.11.0
What was the last working version of Home Assistant Core?
core-2023.10.5
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
The integration is failing to start so I don't have an option to download diagnostics data, but the logs look useful.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response