Note that Enbrighten devices sometimes need to be power cycled #3319
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had two different Enbrighten devices stop responding over the past two days. In the past, I've just power cycled them but not figured out why they were not working.
Today, I sniffed the traffic, and discovered that the coordinator had no route to the device such as:
While I could see
Route Requestcommands being sent, there were noRoute Recordresponses coming from the devices. This was even though I could see occasional link status broadcasts coming from those devices.As soon as I power cycled the devices, I saw them sending
Route Recordresponses and all was good again.I don't see any bug in herdsman for this and think its' an issue with the Enbrighten devices. I've seen this behaviour across a few different models, so I wouldn't be surprised if they all had this issue. Enbrighten has never issued a firmware update for Zigbee devices, so I think we should put this warning in the docs. I know between this and jascoproducts/firmware#127, I wish I had used a different vendor!