Closed philippmeixner closed 1 year ago
I just found a fix for my issue. When I started my old raspberry back up, it asked me to press the button on the the hue bridge (as always after a reboot). It then showed me a full username:password pair in the logs, whereas the docker instance would have the password 'undefined'.
I copied the password over and added the hosts info, after which the docker instance was able to connect to my hue bridge. Unfortunately I have to re-link the new instance to homekit, but at least it should be working now.
Issue
Homebridge fails to start with authorisation errors in log.
I had homebridge hue running on my Raspberry for years, now I'm setting it up on my Truenas Scale machine in a docker container. Since I experienced this issue when restoring from my backup, I tried to do a fresh install of homebridge and the hue plugin, but I still have the same error.
After the fresh install, the plugin asked me to put the generated user info in the config and restart. After that the authorisation error is thrown on startup. I tested my other plugins (shelly, tp-link) separately which work without issue (found existing accessories and can control them).
I don't remember having to do any hue user configuration on my Raspberry setup, and there also is no 'user' entry in my old hue platform config. My Raspberry instance still works fine (was unplugged when setting up new instance).
The container has a static IP and I can access the web UI just fine.
Log Messages
Debug Files
Error - Homebridge Hue dump file does not exist yet.
homebridge.log.txt