-
Notifications
You must be signed in to change notification settings - Fork 181
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
Illuminance Measurement for automation #1
Comments
This issue seems to only be a problem with the new app. Could someone take a look at the code to see how to fix this. The illuminance is not exposed for use in automations. |
Hi @coolhand72 ! |
Any updates regarding this issue? |
I've implemented illuminance support for the new app. It just needed a small change in the vid. Pull request: #5 |
Hi, thanks for this. I've just bought a Hue Motion Sensor, and I'm not seeing any readings for illuminance in the old or new app, or in device logs. Additionally there is an error. Log lines below. I don't have a Hue Bridge to test that the illuminance sensor actually works in my device.
|
I had the same issue! |
I don’t have a hue bridge so can’t do that. Is there another way?
EDIT: ok, weirdly it has started working. Not sure what that was about.
… On 7 Apr 2020, at 14:00, Ra7t0r ***@***.***> wrote:
I had the same issue!
So should update firmware on your hue motion sensor via hue bridge.
Everything will should work fine after that
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The illuminance value works perfectly in WebCore. I can now get rid of Hesperus, and I only need a couple of HomeKit automations for switching Nest Cams and Thermostat on and off. Not so many complex automations to lose whenever HomeKit decides to wipe them. |
Really good work it seems that all works fine!
can you please add the feature that we can use the Illuminance Measurements for automation?
for example:
if the lux falls under 20 the light should go on.
The text was updated successfully, but these errors were encountered: