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

Philips Ambilight can't find the diyHue bridge #988

Open
galaxxy22 opened this issue Jan 22, 2024 · 8 comments
Open

Philips Ambilight can't find the diyHue bridge #988

galaxxy22 opened this issue Jan 22, 2024 · 8 comments

Comments

@galaxxy22
Copy link

Issue does not already exist?

I have searched and found no existing issue

Select Environment

Docker

Home Assistant related?

No

Description

I have tried installing diyHue via HomeAssistant and Docker. When I go to the settings of the TV and try and search for bridges, it only finds my original Philips Hue bridge, but not the diyHue bridge. The Hue app and Essentials app do add it succesfully.

There was actually one short time I did see it show up, but after adding it, it wouldn't work and was gone again.

Both the TV and diyHue are on the same network.

Errorlog:

I don't know where to find the logs

Steps to reproduce

  • Go to the ambilight settings of the TV
  • Search for available bridges

Please enter your operating system details here

DiyHue latest version running on Docker running on a Linux server running on a VM in Virtualbox.

What DiyHue version(branch) are you using?

master (latest)

@mariusmotea
Copy link
Member

There are two methods to discover a Hue Bridge. Using local LAN services or using cloud based services. It is more easy to do it using cloud based services and because wich will not work with diyHue. Since your TV may have a successful discovery using cloud services (the original bridge) it will not fall back to local LAN discovery.

@galaxxy22
Copy link
Author

There are two methods to discover a Hue Bridge. Using local LAN services or using cloud based services. It is more easy to do it using cloud based services and because wich will not work with diyHue. Since your TV may have a successful discovery using cloud services (the original bridge) it will not fall back to local LAN discovery.

That makes sense. Any idea how to fix this? Disable the Philips Hue bridge temporairly?

@mariusmotea
Copy link
Member

yes, but i think you need to keep it disconnected with more than 30 seconds before to perform a bridge discovery.

@mariusmotea
Copy link
Member

Check by accessing https://discovery.meethue.com/ , it need to return [] when no bridges are registred to online discovery service.

@galaxxy22
Copy link
Author

Check by accessing https://discovery.meethue.com/ , it need to return [] when no bridges are registred to online discovery service.

This already returns [] for me without disabling the Hue bridge

@mariusmotea
Copy link
Member

most likely you are not in the same network.

@galaxxy22
Copy link
Author

I restarted the Hue bridge, the found it https://discovery.meethue.com/. Then disconnected again and managed to connect the TV to the diyHue bridge! Unfortunatly when I connect the Hue bridge again, after a few minutes the TV connected lights stop working, it was also quite laggy, but that might be because it is only a ESP8266

@mariusmotea
Copy link
Member

ESP lights work better than original ones in entertainment. But if the tv is older it don't use the entertainment protocol, but regulat http api with 1 request/second.

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