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

(Ambilight+Hue) - Transition time can't be disabled/changed when using Zigbee2Mqtt #872

Open
2 tasks done
joaquinvacas opened this issue Nov 13, 2022 · 2 comments
Open
2 tasks done

Comments

@joaquinvacas
Copy link

joaquinvacas commented Nov 13, 2022

Describe the bug

Running latest diyHue stable version, Docker container, no issues at all, working flawlessly with Ambilight+Hue on a Philips TV for months.

Problem here is that the entertainment mode can't adjust transition time, it seems to be hard-coded.

I mean, using a WiFi bulb (tried a Tasmota bulb I had at home) the transitions between changes are instant, with no transition time.
Which makes the experience feel real good, as diyHue can sync the bulb color at the same time than the TV, as it was expected in a real Hue Bridge with Ambilight+Hue.

When using Zigbee2mqtt, Philips Hue bulbs set with transition at 0, it keeps making some "fade" transition between all states.

Tried everything, but diyHue UI doesn't show any kind of config for changing this.

Steps to Reproduce

  1. Add Zigbee2mqtt color bulb to diyHue
  2. Pair diyHue to Philips Ambilight + Hue on TV
  3. Watch some content

Expected behavior
Sync at time, with no fade/transition, as other bulbs do.

Logs
No logs.

Docker Info (please complete the following information):

  • Architecture (Ex: x86, ARM): x86
  • Docker image version (Ex: latest, arm-05f043b, 128): latest
  • OS (Ex: Windows 10, Ubuntu Buster): Debian 11
  • Hardware (Ex: PC, Raspberry Pi 1/2/3/Zero): x86 Server

Checklist

  • I confirm that this is a bug report
  • I confirm that I have completed this template to the best of my ability

Additional context

@mariusmotea
Copy link
Member

mariusmotea commented Nov 15, 2022

Hi,

Supporting multiple types of lights with entertainment protocol required lot of tuning because some lights types are faster than other. ZigBee lights are somewhere in the middle, they can play nicely if the lights have good connection to the coordinator or bad if they using multiple proxy devices to reach the coordinator. Looking at the code i notice that we put a transitiontime value, but i think some lights may ignore it:

https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/services/entertainment.py#L204-L207

I recommend you to mount this file from host in the container and try various values (restart the container on every change).

Also note that in order to create a better entertainment experience with slow protocols we created a function that skip the frames that don't differ too much from the previews one and this can be tuned here:

https://github.com/diyhue/diyHue/blob/master/BridgeEmulator/services/entertainment.py#L12-L13

GitHub
Main diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.
GitHub
Main diyHue software repo. Contribute to diyhue/diyHue development by creating an account on GitHub.

@mariusmotea
Copy link
Member

Also feel free to create a pull request if you find better values for this protocol so with the future updates you don't need to apply manual changes.

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

2 participants