forked from zigpy/zigpy-zigate
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
- Loading branch information
Showing
2 changed files
with
9 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
88d1cb6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you force the value to "true" but does that fix fix the issue ? ( zigbee network instability ) ?
thanks
88d1cb6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The warning has no impact on network stability. All it means is the
ZiGateDevice
Python object has no node descriptor and no initialized endpoints, nothing more.I don't have a ZiGate device to test with but if you want to try, see if this change works (https://github.com/zigpy/zigpy-zigate/blob/dev/zigpy_zigate/zigbee/application.py#L58):
dev = ZiGateDevice(self, self._ieee, self._nwk) + await dev.initialize() self.devices[dev.ieee] = dev
Not all coordinators support sending requests to themselves but if it works then calling
dev.initialize()
is the correct fix.