Closed askovi closed 3 years ago
I think what happened is that the bridge creator during the plugin installed pre-populated the port input with a port already in use by one of the 2 other bridges.
I think I’m having a similar issue. Except after about a minute the UI just goes to the loading screen and then the Pi drops off the network completely and the recovery webpage and SSH doesn’t work either of course so I can’t even grab any logs. Ring plugin always works whether I install and spawn a new bridge or add to empty bridge. I did the same with Ford Pass and it crashed when it spawned a new second bridge but when I added it to a second empty bridge it worked (on the second re-image - plugin didn’t work though) and then I added Hue and auto spawned the third bridge and then boom Pi dropped off the network again after about 3 or 4 mins after installing hue plugin (didn’t even have time to press the link button) Pi is connected via Ethernet. Would love to supply logs but I just can’t get em haha. When it happened the first time I was pretty sure it’s because both bridges were using the same bridge port but I forgot to write them down when creating the bridges and couldn’t find how to find what bridge port and active bridge is using after it’s created.
I have a port in use error also, however, I only created a single bridge. I run hubitat-makerapi, dummy-switches, myQ and camera-ffmpeg at the moment
I made sure it’s not using same bridge port as HomeAssistant’s homekit integration or HomeBridge but do native home hubs like lutron or hue use the same bridge port type linkage and if so how can we ensure we don’t overlap those bridge ports by accident.
This seems to also occur when playing around with the bridge settings such as Generate New Identifier, changing the Bridge Advertiser, etc.
The bridges weren't shutting down properly. I have this fixed in 4.0.39.
Related to #30
It stopped on its own after installation then restarted after adding configuration and stopped again. I then manually started it from the bridge page and now it's running. Not sure what caused this so opening this for investigation.