Trouble with Hue Bridge

Hello,

It’s been a few years since I last played with Gladys, and I must say, great progress!

I am having an issue finding my Hue Bridge.

Here is some context:

  • My mini-pc (Ubuntu 24.04.3 LTS) is connected to the router by Ethernet cable.
  • I have Gladys running in a docker compose container (see yml below)
  • When I try find the bridge, nothing shows up and I don’t get the option to add the bridge manually (as per doc)
  • In the browser, on the networking tab, I get the error 500: Error: Problem connecting to bridge ‘192.168.0.167’: connect EHOSTUNREACH 192.168.0.167:80
  • I have the Hue Bridge v2 (the square one).
  • I found this help article that seems to have the same issue but it was resolved.
  • I have restarted Gladys (v4.64.0) and the docker container, no success

$ cat server/compose/gladys/docker-compose.yml

version: "3"
services:
  gladys:
    image: gladysassistant/gladys:v4
    container_name: gladys
    restart: unless-stopped
    privileged: true
    network_mode: host
    environment:
      NODE_ENV: production
      SQLITE_FILE_PATH: /var/lib/gladysassistant/gladys-production.db
      SERVER_PORT: 8081
      TZ: Europe/Dublin
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /home/ubuntu/server/data/gladys:/var/lib/gladysassistant
      - /dev:/dev
      - /run/udev:/run/udev:ro

  watchtower:
    image: containrrr/watchtower
    restart: unless-stopped
    container_name: watchtower
    command: --cleanup --include-restarting
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

https://discovery.meethue.com/ shows this from the box:

This is weird because the bridge is located at 192.168.0.112

It shows the below when testing from the laptop that I use to ssh into the box:


Gladys screenshot:


Bridge is reachable:

$ ping 192.168.0.112
PING 192.168.0.112 (192.168.0.112) 56(84) bytes of data.
64 bytes from 192.168.0.112: icmp_seq=1 ttl=64 time=3.05 ms
64 bytes from 192.168.0.112: icmp_seq=2 ttl=64 time=0.474 ms
64 bytes from 192.168.0.112: icmp_seq=3 ttl=64 time=0.478 ms
64 bytes from 192.168.0.112: icmp_seq=4 ttl=64 time=0.568 ms
^C
--- 192.168.0.112 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3030ms
rtt min/avg/max/mdev = 0.474/1.142/3.050/1.101 ms

and

$ curl https://discovery.meethue.com/
[{"id":"ecb5fafffeab5608","internalipaddress":"192.168.5.105","port":443},{"id":"001788fffe495a3d","internalipaddress":"192.168.0.167","port":443}]
ubuntu@flox:~$ curl http://192.168.0.112
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
    <title>hue personal wireless lighting</title>
    <link rel="stylesheet" type="text/css" href="/index.css">
</head>
<body>
    <script src="/licenses.js"></script>

    <div class="container">
      <h1>hue personal wireless lighting</h1>
      <img src="/hue-color-line.png" class="colorline" />
      <div class="inner-container">
        <p>
            Welcome to hue - your personal wireless lighting system. For more information please see our website <a href="http://www.philips-hue.com">www.phil [...]

After trying a few times, I get Error: Problems resolving hue bridges, Request failed with status code 429 – which I assume it is a waf type of protection.

Any ideas?

Hi @theodore and welcome on Gladys !

Do you know the IP address of your Philips Hue bridge?

You can use apps like:

With the IP address, you can then configure manually the bridge without scanning.

Do you confirm that you click on the Philips Hue bridge physical button before configuring the bridge ?