-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Potential Bug with Homebridge Beta 1.3.0] - Don't use activity id as identifier for input source since it only allow UINT32 #315
Comments
Thanks @nicoduj . FYI, after update, I still receive the error/warning:
|
thank you, will have to test with homebridge beta so, since I removed the -1 I was setting explicitely but seems to have other problems. |
Need to store a map betwwen activityids and input source identifiers as Uint32 (or do some hash magic) |
Thank you for continuing to look into this @nicoduj. Is this something you can/are willing to implement? Noticed it went to closed. Thanks, again! |
I'm seeing this is beta 53 08/02/2021, 15:02:55] The plugin 'homebridge-harmony' slows down requests made to homebridge! The read handler for the characteristic 'Active' was slow to respond! |
Yes, same errors for me with 1.3.0beta47. |
Now that Homebridge 1.3.0 is public, will this warning be addressed soon in a updated release? The error messages are quite frequent. Thanks. |
Working on it, still need to do more tests ... |
Hello,
I am not sure if this can be addressed or not, however, on the latest version of Homebridge beta, I receive the following 'warning' a lot during startup.
Received warning for the plugin 'homebridge-harmony' from the characteristic 'Active Identifier': characteristic was supplied illegal value: number -1 exceeded minimum of 0.
Installation Details:
homebridge-harmony(v1.4.0)
home bridge(1.3.0beta14)
hap-nodejs(0.9.0-beta.43)
Full Log:
The text was updated successfully, but these errors were encountered: