![]() How does this thing differ from the existing solution diyHue ?ĭiyHue was created to be a hub on it's own. We'll provide you with some sample run commands soon. Sure, just run the docker image manually. I run Home Assistant manually without all the supervisor stuff, can I still run this thing ? ![]() Remember to stop the addon before you start editing this file. Set a value (in milliseconds) to throttle requests to this light. If you hardware can't cope up with this we have an advanced little setting hidden in the above mentioned emulated_hue.json config file called "entertainment_throttle". It will send multiple commands per second to each light. When I enable Entertainment mode my light/platform gets overwhelmed with commandsĮntertainment mode is heavy. That will also mark the light as disabled. You can also delete a light in the HUE app. In that file you can disable lights or groups by setting enabled to false. In your Home Assistant config directory you'll find a folder for emulated_hue witha file called emulated_hue.json. Please use the Github issue tracker for feature requests (including motivation) and off course for reporting any issues you may find! FAQ I do not want to have all my Home Assistant lights imported to HUEīy default all your Home Assistant lights and areas will be imported to get you started quickly but you can customize this. Create HUE scenes, push to HASS scenes ?.Forward Entertainment UDP packages to Zigbee mesh for Official HUE lights that natively support the feature.Support other device types, like switches ?.The next step we have in mind is, if you own official HUE lights connected to ZHA, to forward the special Entertainment packets into the Zigbee mesh, resulting in the real streaming experience (realtime effects with no delay). This means that the Entertainment mode will work with any light connected to Home Assistant. We choose some settings which result in a nice effect with not too much delay without completely overloading a platform. ![]() While packets are indeed live streamed (at a rate between 25-50 messages per second) to our virtual bridge, we unpack them and convert them to commands the light implementations can understand at a more sane rate level (throttling). We've created a (highly experimental!) python implementation of this streaming protocol that actually works pretty well altough not as good as it's original. It's used for new Ambilight+HUE TV's and the HUE Sync app on PC and Mac. Using this protocol, it is possible to stream lighting effects to multiple lights in parallel with a high update rate. The Hue Entertainment API supports a communication protocol which allows a light streaming functionality with the Philips Hue System. Notes on Philips HUE Entertainment API support This thing is local only (which is actually a good thing perhaps?). Remote Connection support is not available.If you're running the previous/legacy emulated HUE component in HASS, make sure to disable it first.These ports can not be changed as the HUE infrastructure requires them to be at these defaults. This virtual bridge runs at HTTP port 80 and HTTPS port 443 on your local network.Once you enabled pairing mode, your app has 30 seconds to connect.It will show you a message in the notification area WITHIN Home Assistant. Once the bridge is found by your app/device, there's a notification sent to Home Assistant if you want to enable pairing mode (same as pressing the physical button on the real bridge).From your app/device (for example the official HUE app) search for HUE bridges.Once started, it will be available as a HUE bridge on your network. Start the newly installed addon and it will work instantly.Install the Emulated HUE addon from the addon-store. ![]()
0 Comments
Leave a Reply. |