2 Lutron Caseta bridges causes errors that slow down Homebridge
TerryLeeWhite opened this issue · comments
Describe The Bug:
I have two bridges and Associate one with the plugin. Then the Leap plugin constantly gives an error that it has no credentials for the other bridge that's NOT associated.To Reproduce:
just having two Lutron bridges and associating one.Expected behavior:
not having the 2nd bridge cause errors.Logs:
Show the Homebridge logs here, remove any sensitive information.
[1/4/2023, 8:05:45 PM] [Lutron] Could not connect to discovered hub: Error: no credentials for bridge ID 01F07DD7
at LutronCasetaLeap.handleBridgeDi scovery (/usr/local/lib/node_ modules/h omebridge-lutron-caseta-leap/src/platf orm.ts:180:19)
at BridgeFinder.emit (node:events:
527:28)
at /usr/local/lib/node modules /hom ebridge-lutron-caseta-leap/node_ module s/lutron-leap/src/BridgeFinder.ts:45:2
6
[1/4/2023, 8:05:48 PM] [Ring]
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.Screenshots:
Environment:
- Plugin Version:
- Homebridge Version:
- Node.js Version:
- NPM Version:
- Operating System:
Lutron bridges announce themselves every so often, and the plugin will search for them every so often. When they're found, an attempt is made to connect, and if there are no credentials, an error is printed. This occasional-discovery-and-connection process is by design, and is the only way bridges are ever found. This failure is, in cases such as yours, expected to be benign, and you should be able to ignore it. Is it causing any other problematic behaviors? I'm also open to suggestions about how I can improve the error. Not many people running the plugin have intentionally-unconfigured bridges. :)
Yes the problem is that it slows down my entire HomeBridge. I had to disable the plugin to get all my other accessories to stop saying "updating" or no response. Once I disabled your plugin performance returned to normal. My suggestion would be let us associate all bridges and then pick the primary one.
You could also give us a manual Discover button that we press when we want to set up a new bridge instead of it constantly polling.
Oh that’s quite curious about the slowdown. I’ll have to see if I can reproduce. I’m not sure why that would have happened. Any chance you can give me a complete debug log that shows the error during slowdown?
And thank you for the support!
Now it just got weirder. When I enabled the plugin and DEBUG. It worked well and there was no performance hit. However, as soon as I turned DEBUG off again and rebooted the performance tanked.
LutronLeapDebug-TerryWhite.txt
@TerryLeeWhite
I'd highly recommend setting up the plugin in a Child Bridge.
@MoTechnicalities you're a life saver! That did the trick. Thanks for pushing me to investigate Child Bridges, and set one up. That was my first although I've heard people talk about them since the feature came out. I get it now. It solved the performance problem.
@TerryLeeWhite
Great! Now that you've moved to the Child Bridg, check and remove unneeded cashed duplicates in the Homebridge Settings. You can check the listed devices against the currently working ones found in the Home App. ONLY REMOVE THE UNNEEDED ONES!
I found duplicate cashed accessories (bridge & remotes) linked to the old bridge ID. Have Fun!
thanks! got it.
Holy shit, @MoTechnicalities, that's amazing. Thank you so much for helping @TerryLeeWhite out.
@TerryLeeWhite, I'm going to close this but link it to #92, and will update the README when I have a chance (unless @MoTechnicalities beats me to it, and I might steal those images 😆 )