-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ZHA to also poll Philips Hue lights with new firmware #54513
Update ZHA to also poll Philips Hue lights with new firmware #54513
Conversation
Hey there @dmulcahey, @Adminiuga, mind taking a look at this pull request as it has been labeled with an integration ( |
Signature of an older Hue bulb (ZLL profile) which needs this "fast poll":
|
LWB010 before update:
Adding OTA file and restarting HA:
Looks like the new names is not being loaded by repower the light so i was deleting it and readding and was getting:
Name changed and quirk is not loaded (i dont knowing if its needed after the last commits) but looks working as normal (have not looking if its still not aging out its neighbors and children but its going back in the "Decommissioned things" box). Edit: |
Signature of a newer Hue bulb (ZHA profile) which does not need any special treatment:
Note: The quirk not applying because of cluster change 0xfc02 -> 0xfc03) |
Sorry i was not looking so good my have also getting one 0xfc03 cluster ;-(( Do we needing quirk for fixing on/off and light level after power reset or is it implanted in the ZCL ? |
zigpy/zigpy#716 and zigpy/zha-device-handlers#872 would fully implement ZCL v7 making this redundant. (Still WIP) However, it looks like zigpy/zigpy#774 was merged as a fix for now (not fully implementing ZCL v7) but at least providing @puddly seems to also have implemented that attribute in the pending PR zigpy/zigpy#716. It might be best if PR to add |
Tested and working. In the future, it should be considered to disable the fast polling for newer (ZHA profile) Hue bulbs (only match |
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.
Lgtm
Proposed change
The older Philips Hue lights (ZLL profile) do not send attribute reports and have to be polled more often.
In firmware updates from early this year, Signify changed some of the manufacturer from "Philips" to "Signify Netherlands B.V.". This change was only made to some of the newer-style Philips Hue lights (ZHA profile with Bluetooth). These lights do not have to be polled anymore (hence this changed wasn't made back then).
New firmware which doesn't seem to be fully rolled out yet (not even available through the Hue Bluetooth app yet) also changes the manufacturer name on the older Hue bulbs (which have to be polled).
These new firmware images can be found here: Koenkk/zigbee-OTA#47
I'll still have to test this minor change once I get all different types of Hue lights updated. I'll update the PR.
Also, would it (easily) be possible to only match
HueLight
to the older (ZLL profile) Hue bulbs?Signature of an older Hue bulb (ZLL profile) which needs this "fast poll": https://paste.ubuntu.com/p/RKbpqqD4Rt/
Signature of a newer Hue bulb (ZHA profile) which does not need any special treatment:
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: