986ster

Anyone have any ideas how to diagnose this? I'm dead in the water when I can't get HA to talk to my Caseta bridge at all, which means I can't...

I did a total rebuild on this Intel hardware using the 2025.3.1 image and tried to add the discovered Caseta bridge as the first integration in this totally clean build...

Are you running HAOS, or a Docker or bare metal install for yours? I have another instance of HAOS on an RPi on the same subnet at the x86_64 machine...

My HA servers and Caseta bridges are on two different subnets. If I allow my servers to initiate any sessions to the IoT subnet (where the bridge is) then the...

How do we go about getting it resolved then? I can't realistically be expected to move my HA server to a different subnet every time I want to add a...

I've never had this working for me in an earlier version of HAOS, so I don't know if it broke at a point in time. My current HA server is...

That is indeed my post. I did try changing my locale as well though, so I'm pretty sure that having it in en_GB didn't make any difference whatsoever. I can't...

@bdraco I can't add debug logging to an Integration that's Discovered but not yet Configured. The whole problem here is that it detects the Caseta bridge, but the actions to...

I had to put logging in debug mode to try to find anything related to this, and there are only two lines in the log that reference pylutron_caseta: ``` 2025-03-16...

Okay, so slightly different behaviour with this version. The UI reports: [%key:common::config_flow::error::cannot_connect%] after the Pair with the bridge popup The log has only the one line: 2025-03-17 21:59:56.516 INFO (SyncWorker_0)...