![]() ![]() Its connectivity is good enough to respond. Listed as unavailable in the hue app, but responds to the hue app. If a light is unavailable in the Hue app and HA it means that its a) powered off or b) having issues with connectivity, bad reception or c) not routing at all, such as most (all?) OSRAM lights if connected to a Hue zigbee mesh.Īgain. I'm talking to this via the hue hub though not ZigBee so. The unavailable state is correct: It is attached to the "zigbee connectivity" of the device. ![]() The direct service calls seem to accept it though. The HA frontend doesn't allow controlling unavailable entities. I think its 100% correct, at least the V2 api is from I've seen while working on this last couple of months. If the API is not correct you should probably file an issue report with Signify -) That situation will be auto detected by the HA integration and the availability check will be disabled. If a light is unavailable in the Hue app and HA it means that itsī) having issues with connectivity, bad receptionĬ) not routing at all, such as most (all?) OSRAM lights if connected to a Hue zigbee mesh.īoth b and c can be killing for the performance/reliability of your entire setup, although it can be pretty safe to ignore case c if you have enough other lights available that route properly and those bad behaving lights can reach the bridge directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |