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

New Hue API with push #227

Closed
Flothoger opened this issue Aug 26, 2021 · 9 comments
Closed

New Hue API with push #227

Flothoger opened this issue Aug 26, 2021 · 9 comments

Comments

@Flothoger
Copy link

The time delay with polling is pretty frustrating when dealing with motion sensors. I recently read that the bridge got a new api with push. This should mitigate the problems of polling, because the bridge is sending changes directly to the application.

So far, however, the new API does not seem to be documented by signify.

If it is possible to implement will this be planned for a future version of the adapter?

The article I have read: https://www.smarthomeassistent.de/neue-philips-hue-api-arbeitet-per-push-schnellere-kommunikation/

@foxriver76
Copy link
Member

We would like to continue to use the node-hue-api, thus we will wait until peter-murray/node-hue-api#202 is implemented. We could also rely on https://github.com/homegraph/philips-hue-push-client, but that doesn't fit that well in our infrastructure and is likely to be not as well maintained as node-hue-api

@Pmant
Copy link
Contributor

Pmant commented Aug 28, 2021

You can try this script until the push API is officially supported.

@Flothoger
Copy link
Author

You can try this script until the push API is officially supported.

That works realy well, at least for now. Thank you for the suggestion.

@klein0r
Copy link
Contributor

klein0r commented Nov 14, 2021

Some official information:

Hue API V2

The Hue API - referred to as CLIP API ('Connected Lighting Interface Protocol') - will move to version 2, which is a breaking change over version 1. Version 2 is still a RESTful JSON HTTP API, but the structure has been redefined to make some improvements and allow for new use-cases. Both APIs will exist in parallel to give developers time to upgrade, however any new features (such as dynamic scenes) will only be available on V2, and in the long term the V1 API will eventually be removed. The V2 API is currently in early access and not yet feature complete, but it is already available on production bridges and in use by Signify developed applications. For features that are available on both versions, we recommend to start using V2. Just make sure to check that the bridge version is at least 1948086000.

https://developers.meethue.com/develop/hue-api-v2/

As per today, we deprecate UPnP as a local bridge discovery method, scheduled to be disabled in Q2 2022. Please use the recommended discovery methods mDNS and discovery.meethue.com which are supported since January 2018.

https://developers.meethue.com/new-hue-api/

@BigMike71
Copy link

any news about updating the adapter to the new Push Api?

@foxriver76
Copy link
Member

Still peter-murray/node-hue-api#202

@BigMike71
Copy link

how can i use it with iobroker? its a plugin?

@klein0r
Copy link
Contributor

klein0r commented Jun 1, 2022

@BigMike71 It is not a plugin, it's a library (which is used by the ioBroker hue adapter). This library has to be updated (see linked issue). After that, this adapter can be updated to use the latest version of that library.

@rug1024
Copy link

rug1024 commented Dec 29, 2022

Please make this happen, the workaround script by Pmant worked out of the box but not for long, after some time states just were not updated anymore. IKEA Tradfri does 'push' since always, did'nt even know that this issue exists when changing my whole home to Philips Hue.

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