Tracking Zigpy issues

[pipiche38]

We are tracking here all of the open issues against zigpy and zigpy related radio modules, which are impacting the plugin

zigpy

• backup between bellows and znp zigpy/zigpy#1016
• aligning ZNP and Bellows configuration zigpy/zigpy#1011
• What handling recommandation when receiving ControllerException zigpy/zigpy#1000
• Bellows exception zigpy/zigpy#999
• How to manage Default Response when not using the ZDO/ZCL zigpy layers ! zigpy/zigpy#985
• Zigbee network size zigpy/zigpy#970
• Is zigpy radio librariew works on Windows system zigpy/zigpy#949
• Python3.7 zigpy/zigpy-znp#198
• Failed to deserialize ZDO packet / Data is too short to contain 1 bytes zigpy/zigpy#1131
• zigpy depends on rpds since 0.63.5 zigpy/zigpy#1375 ( PyO3 modules do not yet support subinterpreters crate-py/rpds#63 )

zigpy/bellows

• Not able to run bellows cli zigpy/bellows#458
• WARNING :NWK conflict is reported for 0x6452 zigpy/bellows#465
• Not able to start zigpy/bellows since the latest update of master zigpy/bellows#468
• [zigpy] - error during runtime #1200

zigpy/znp

• Remote serial via tcpip zigpy/zigpy-znp#156
• ValueError(f"Data is too short to contain {byte_size} bytes") on IEEE Addr Request zigpy/zigpy-znp#155
• asyncio.TimeoutError when permit to join on specific router zigpy/zigpy-znp#154
• ZNP / CCxxxx - unable to send command/message to a Battery based end device operating with polling #1341
• Unable to start zigpy-znp zigpy/zigpy-znp#204

zigpy/deconz

• Setting Manufacturer ID zigpy/zigpy-deconz#187
• [zigpy-integration] Allowing Endpoint allocation on ConBee/RaspBee for Livolo, Schnider and fancy devices #1145
• Network Update Request to change network channel does'nt work zigpy/zigpy-deconz#192

[pipiche38]

up

[Hedda]

We are tracking here all of the open issues against zigpy and zigpy related radio modules, which are impacting the plugin

zigpy

• aligning ZNP and Bellows configuration zigpy/zigpy#1011
• What handling recommandation when receiving ControllerException zigpy/zigpy#1000

If you want these to be followed as issues by the upstream zigpy project then suggest (re)submitting them as new issues instead:

https://github.com/zigpy/zigpy/issues

https://github.com/zigpy/zigpy/issues/new

Issues tend to be more formal tasks, feature requests and/or bug reports which can more easily be tracked with a status.

https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues

Discussions on GitHub are just an informal communication channel which are not tracked or followed up as issues are.

https://docs.github.com/en/discussions/guides/best-practices-for-community-conversations-on-github

https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/about-discussions

Discussions can still be cross-referenced in issues and vice versa, and people with triage permission to a repository can even create an issue from a discussion, (but then you have to get a project admin to do it so probably easier to just create new issues).

https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-discussion

[pipiche38]

new issue reported with zigpy 0.63.4

zigpy/zigpy#1375
crate-py/rpds#63

[pipiche38]

new issue reported with zigpy 0.63.4

zigpy/zigpy#1375 crate-py/rpds#63

workaround in place as discribed in the zigpy discussion