Failed setting up Pico remote about homebridge-lutron-caseta-leap HOT 11 CLOSED

Curious, I don't know what could cause this. This means that Homebridge was able to talk to the bridge, but the bridge took too long (> 3 seconds) to respond. Is the network reliable, or do you have anything else talking to the bridge?

from homebridge-lutron-caseta-leap.

Network is reliable and the bridge only communicates with homekit. Any homekit to Caseta commands respond almost instantaneous.

from homebridge-lutron-caseta-leap.

Installed v2.2.1.
Not sure if this means anything. I disabled insecure mode and the picos seemed to "set up". When I switched back to insecure, the timeout issue returned.

[1/28/2022, 07:59:58] [Lutron] Finished setting up Pico remote Living Room Floor Lamp Remote 1
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Living Room Bottom Stairs
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Living Room Top Stairs
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Kitchen Kitchen Preset
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Table
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Guest Bedroom Pico
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Basement Stairs Pico 1
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Basement Stairs Top
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Master Bedroom Pico
[1/28/2022, 07:59:59] [Lutron] Finished setting up Pico remote Living Room Alarm Mica
[1/28/2022, 08:00:20] [Homebridge UI] Homebridge must be running in insecure mode to control accessories

from homebridge-lutron-caseta-leap.

Weird. I don’t honestly don’t understand what that toggle does, but it’s enabled by default and I’ve never tested … well, anything at all, really, without it.

from homebridge-lutron-caseta-leap.

Add this one to the weird behavior I’ve seen. This started happening to me today. I noticed at first that my Picos stopped working, then restarted my homebridge and got these timeouts in the logs. Can’t seem to get it working now. I restarted the lutron hub and homebridge server. Both are hardwired on the network.
The plugin still discovers all of my connected devices, but times out at set up so the devices won’t work. Does the timeout here just need to be a bit longer?

oh, and turning off insecure mode doesn’t change anything.

from homebridge-lutron-caseta-leap.

I manually changed the timeout in BridgeManager from 5 to 7 seconds to solve this for me. That does seem like a long time to wait for a response though. Maybe this could be configurable in the future.

from homebridge-lutron-caseta-leap.

You’re running it on an RPi, right? Which model? I have a growing suspicion that a lightly loaded Pi slows nodejs down a bunch.

from homebridge-lutron-caseta-leap.

Pi 3B+

from homebridge-lutron-caseta-leap.

it feels like papering over the problem to just increase the timeouts, but it sounds like that's what's actually warranted, eh?

from homebridge-lutron-caseta-leap.

I agree with you. I'm fine to leave mine as a custom edit. I wouldn't change it for everyone unless it was a configuration option.

from homebridge-lutron-caseta-leap.

[edit: in v2.3.0-beta9, which will be fully released soon] I've increased the timeouts to values long enough that Homebridge will actually give up on the characteristic read/write action. I should rein them in at some point in the future, but I'm basically as permissive as I can be. Hopefully this helps prevent problems when you get unlucky w/ slower hardware.

from homebridge-lutron-caseta-leap.