zGuy981 Posted Saturday at 03:50 PM Posted Saturday at 03:50 PM I recently lost all connection to the bridge. Prior to this everything worked fine, I was able to connect and see all lights and scenes. Then it just stopped working after a power outage. When I go in to the logs I see it could not find the bridge, so I manually added it using the `bridges: ["192.168.7.139"]` setting. Except now it's throwing two errors, it's not able to read config file. 2025-08-09 08:40:30.537 Thread-2 (parameter_handler) udi_interface INFO hue:connect: Reading bridges configuration: ['192.168.7.139'] 2025-08-09 08:40:30.537 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Attempting to connect to the bridge... 2025-08-09 08:40:30.538 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Error opening config file, will attempt bridge registration 2025-08-09 08:40:40.546 Thread-2 (parameter_handler) udi_interface ERROR phue:request: POST Request to 192.168.7.139/api timed out. Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902602b_1/phue.py", line 739, in connect with open(self.config_file_path) as f: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/var/polyglot/pg3/ns/0021b902602b_1/.python_hue' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902602b_1/phue.py", line 653, in request connection.request(mode, address, json.dumps(data)) File "/usr/local/lib/python3.11/http/client.py", line 1303, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/local/lib/python3.11/http/client.py", line 1349, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/local/lib/python3.11/http/client.py", line 1298, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) Quote
Geddy Posted Saturday at 10:18 PM Posted Saturday at 10:18 PM @zGuy981 be sure the router is reserving the IP for the Hue bridge. More than likely it wasn't and it's changed IP. Even with your bridge addition it might have changed again. I would check the IP address of the hue hub. Make sure it's being reserved at the router side. Then power cycle everything. power down/unplug eisy unplug hue hub plug in hue hub wait for it to be online/stabilize plug in eisy wait for it to come up and stabilize It looks like you're using the proper "bridge" and ["##.##.##.##"] setting. Not sure why it wouldn't be catching it. You might need to restart the plugin and put the button on the hue hub (within a few seconds) to make the connection again. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.