-
Notifications
You must be signed in to change notification settings - Fork 21
[New feature]&[Bug] "Permit join" for specific router #186
Comments
I successfully force router to permit join by using raw command service, but I face another problem while adding device. Device was added, but ieee address wasn't know at that time, but few second later, which cause a problem to update old entity in home assistant. The new entity was create and two entities for the same ieee exists :-/ Logs from adding:
After restart Home Assistant the entity new one with addr only disappeared and only old one left, which is desynchronized and mark as unavaliable. |
It looks like I restart HA before autosave was trigger, that's the reason of disappearing entity. |
Workaround: In case of paring/reparing device with specific router. HA show duplicated entities, but after waiting 5min after paring (to be sure that autosave happened) and restarting HA duplicates entity disappear and everything looks normal. |
According Koenkk/zigbee-herdsman#81 it's possible to permit join for specific router only. This should help in case of some aqara sensors like (door sensor) which rejoin to network in on specific way not compliant with standard, so zigate coordinator doesn't see sensor after few days (after try to rejoin). Probably joining to aqara wall swich (with neutral - act as router) should solve the problem because it's aqara router.
It will be nice to have also button from UI or at least parameter in service with address or entity.
The text was updated successfully, but these errors were encountered: