Open pipiche38 opened 2 years ago
up
We are tracking here all of the open issues against zigpy and zigpy related radio modules, which are impacting the plugin
zigpy
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
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).
new issue reported with zigpy 0.63.4
https://github.com/zigpy/zigpy/discussions/1375 https://github.com/crate-py/rpds/issues/63
new issue reported with zigpy 0.63.4
workaround in place as discribed in the zigpy discussion
We are tracking here all of the open issues against zigpy and zigpy related radio modules, which are impacting the plugin
zigpy
zigpy/bellows
zigpy/znp
zigpy/deconz