Skip to content
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

Repeated Errors/Requests #50

Closed
ZoneMR opened this issue Jan 18, 2017 · 2 comments
Closed

Repeated Errors/Requests #50

ZoneMR opened this issue Jan 18, 2017 · 2 comments
Labels

Comments

@ZoneMR
Copy link

ZoneMR commented Jan 18, 2017

I have some Osram Gardenspot RGB lights, which currently seem to be unreachable. Every heartbeat I get the following entries in the console log:

[1/18/2017, 6:19:18 PM] [Hue] Wonderland Perimiter: set homekit hue from NaN˚ to NaN˚ [1/18/2017, 6:19:18 PM] [Hue] Wonderland Perimiter: homekit hue changed from NaN˚ to NaN˚ [1/18/2017, 6:19:18 PM] [Hue] Wonderland Perimiter: set homekit saturation from NaN% to NaN% [1/18/2017, 6:19:18 PM] [Hue] Wonderland Perimiter: homekit saturation changed from NaN% to NaN% [1/18/2017, 6:19:18 PM] [Hue] Philips hue: hue bridge request #1225: put /lights/25/state {"xy":[null,null]} [1/18/2017, 6:19:18 PM] [Hue] Philips hue: hue bridge error 7: invalid value, [null,, for parameter, xy [1/18/2017, 6:19:18 PM] [Hue] Philips hue: hue bridge request #1226: put /lights/25/state {"xy":[null,null]} [1/18/2017, 6:19:18 PM] [Hue] Philips hue: hue bridge error 7: invalid value, [null,, for parameter, xy

It seems to be firing off two requests to the Hue bridge and spamming the log with errors. The Hue bridge returns this status for the light when queried manually.

"25":{"state":{"on":true,"bri":254,"hue":0,"sat":0,"effect":"none","xy":[0.0000,0.0000],"alert":"none","colormode":"hs","reachable":false},"type":"Color light","name":"Wonderland Perimiter","modelid":"Gardenspot RGB","manufacturername":"OSRAM","uniqueid":"84:18:26:00:00:08:d6:0c-03","swversion":"V1.03.20"}

@ebaauw
Copy link
Owner

ebaauw commented Jan 19, 2017

Apparently, the routine that converts the Hue bridge xy values into HomeKit Hue and Saturation values chokes on [0.0, 0.0]. It takes a non-Philips light to reveal this, as Philips lights cannot display this value, and the conversion routine (which I copied from Philips) first translates the value to the closest value the light can display. While I don't have any non-Philips colour lights, I was able to reproduce the error using a group (where the check whether the light can display the value is not done, just as for non-Philips lights).

I need to debug the colour conversion routine to find out where it breaks and how to fix that. As a workaround to stop the log spam, you should be able to change the light's colour from HomeKit (even though the light is unreachable), or failing that, from the Hue app.

@ebaauw ebaauw added the bug label Jan 19, 2017
ebaauw added a commit that referenced this issue Jan 19, 2017
@ebaauw
Copy link
Owner

ebaauw commented Jan 19, 2017

Fixed in v0.1.14.

Division by zero error when the y value is 0.0.

@ebaauw ebaauw closed this as completed Jan 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants