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

Discussion: Hue Emulation and Hue API V2 #17762

Open
andrewfg opened this issue Nov 18, 2024 · 11 comments
Open

Discussion: Hue Emulation and Hue API V2 #17762

andrewfg opened this issue Nov 18, 2024 · 11 comments
Assignees

Comments

@andrewfg
Copy link
Contributor

For discussion: does Hue Emulation need to be rewritten using Hue API V2? (I believe it is currently based on API V1 which may no longer be supported..)

https://community.openhab.org/t/hue-emulator-alexa-app-only-displays-one-light/159556/14

@andrewfg andrewfg self-assigned this Nov 18, 2024
@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/hue-emulator-alexa-app-only-displays-one-light/159556/14

@andrewfg
Copy link
Contributor Author

@davidgraeff @digitaldan => any thoughts?

@jlaur
Copy link
Contributor

jlaur commented Nov 18, 2024

Hue API v2 support would be nice. However, at the same time it's also important to keep support for Hue API v1. For the Hue emulation it doesn't matter how long API v1 will be supported by Signify, the only thing that matters is how long third party integrations will support it. As an example, Logitech Harmony will only ever support Hue API v1.

@andrewfg
Copy link
Contributor Author

only thing that matters is how long third party integrations will support it

Indeed. Good point. But I suppose that if/when Signify does drop it then the third parties must immediately switch to V2 anyway.

it's also important to keep support for Hue API v1

Ok. Understood. But it seems from the referenced community thread that the V1 emulation is, was, or has become broken. And apparently there were no recent breaking changes on the OH side. (??) So presumably this break is something on the third party side. This means that someone here needs to commit to active further development of the V1 emulation to match changes on the the third party side. => Any volunteers? ;)

@lolodomo
Copy link
Contributor

I believe noone is really maintaining the hue emulation binding since years.

@digitaldan
Copy link
Contributor

The binding as it is today was completely re-written from when i originally wrote it (which was a good thing, my version was more like a proof of concept) so i don't have much of a opinion.

That being said, as @jlaur points out, legacy devices will probably support V1 for a long long time.

And for newer devices, the upcoming Matter binding i'm working on allows users to expose openHAB items as Matter devices, so that Google, Apple, Amazon, Smart Things or any other matter client can control it, which is basically the same functionality as this binding. I guess my thought is that this binding is still needed for legacy devices who only talk HUE, and most other things can be supported with Matter.

@andrewfg
Copy link
Contributor Author

andrewfg commented Nov 19, 2024

@digitaldan many thanks for the feedback. As mentioned in the community forum thread above, it seems that some users have an issue when trying to link OH items into Alexa via this Hue Emulation, and I am trying to find the way forward to fix that. I think the summary of the posters here so far are saying not to mess with this integration too much, and basically to focus on maintenance fixes only. So I am trying to find out who we can 'volunteer' to do that work.

@MikeJMajor
Copy link
Contributor

I've been patching up the hue emulator over the years to keep it working with Alexa.

I'll volunteer since trying to reproduce the issue has messed up my working Alexa setup.

@andrewfg
Copy link
Contributor Author

Many thanks to @MikeJMajor for fixing the bug.

I think this means that there is no need to migrate the emulation to API v2. When Philips / Signify finally drops support for v1 this will force the third party integrators to drop v1, and switch to another integration pathway. Most probably this will be Matter rather than them having to support multiple new pathways. And I suppose -- therefore -- that Philips / Signify will not drop support for v1 until their Matter implementation is fully working. (Which currently is definitely not the case..)

@lolodomo
Copy link
Contributor

that Philips / Signify will not drop support for v1 until their Matter implementation is fully working. (Which currently is definitely not the case..)

By curiosity, what is not working with Matter ?

@andrewfg
Copy link
Contributor Author

what is not working with Matter ?

If you look at the Hue developer forum there are still quite a few people complaining about issues. To sum up in a few words, it is probably a) stability issues, and b) interworking issues between different Matter platforms (I would say that the Matter "standard" is not completely standard yet, and different manufacturers are not (yet) fully aligned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants