-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Bug] Device value less than 1% showing 100% in HomeKit #673
Comments
Can you make a PR for this? |
Here is a short clip showing the problematic behavior, notice around 10s when the brightness value is 1 the percentage shown in Home app goes all the way to 100%. Screen.Recording.2023-04-27.at.8.02.23.PM-1.mov |
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions! |
I can confirm that's a UI/UX bug in the Home app, iOS 17.2 still being affected. |
Is there an existing issue for this?
Describe the bug
I have IKEA TRADFRI bulbs that could be dimmed all the way down to 1/254 reported value in Zigbee2mqtt, or 0.39%. For some reason when the percentage value goes less than 1 it will be mistakenly reported as 100% in the Home app...could be an Apple thing for them to fix, but in the meantime could we implement this to monitor.ts?-
This will help HomeKit read less than 1% values somewhat correctly.
I believe the change should only affect lights and battery percentages.
Related devices
and potentially other bulbs.
Related Devices
No response
Steps To Reproduce
Expected behavior
Expect in the Home app that the reported value should correctly follow the calculated percentage even when it's less than 1%.
Device entry
No response
Status update
No response
Messages from this plugin
No response
This plugin
1.9.2
Homebridge
1.6.0
Zigbee2MQTT
1.30.3
Homebridge Config UI X (if applicable)
No response
The text was updated successfully, but these errors were encountered: