Lutron Caseta Support

Frenchman · October 27, 2020, 10:56pm

By the way, I believe there actually IS a way to adjust the fade times on the Caseta dimmers, but it is somewhat involved. You would need to set up the LEAP bridge and send some custom LEAP commands to do the configuration using the bridge’s debug channel.

I’m totally willing to do this :D. What’s interesting too is that apparently the fade time is more tolerable (i.e. faster) when I use the switch than when the command comes from the paired Pico keypad. I’ll have to investigate. I don’t think it’s a delay (like due to the bridge), it really seem that they use different fade durations…

Frenchman · October 28, 2020, 3:08am

I do understand the high end vs lower end predicament. At $120 for a Radio RA2 switch there should be enough margin for a few intermediaries, for sure! I also agree with you that it doesn’t seem like a smart long term strategy. I am already looking to see if I can find better switches and dimmers Though honestly if I can fix the fade times to be shorted and consistent I may call what I have good enough. I write software for a living, I don’t want to spend all my free time writing more software for lighting In any case it seems like the remotes are a good investment given I have the bridges because I could use them to trigger anything else I want.

BobA · October 29, 2020, 10:33pm

I know that I ran across instructions on how to do this somewhere while I was researching the LEAP protocol, but now I can’t seem to find it again. You may want to try your own luck with google. There isn’t all that much info out there on LEAP, so the number of sites to choose from will be pretty limited. It may have been in one of the HA forums, or possible in an issue on github somewhere. In the meantime, I’ll keep looking.

I tend to like moderate fade-up times and fairly long fade-down times on my dimmers, but everyone has a different opinion in it. Have fun arguing about it with your family!

morph166955 · October 31, 2020, 4:08pm

@BobA I’ve noticed one issue with the LEAP integration (which likely could have been there with the IP version, I just never noticed it). I’ve had instances where an update is “missed”. For example, I have a pico which is connected to all the lights on my first floor (one button on/off for the house). It’s all done via the lutron hub, nothing of that pico is done in OH. If I use it, from time to time some of the items in OH don’t catch the change. I’ve also noticed this behavior if I push a whole bunch of light changes from OH (e.g. scene change). This is causing some of my rules to freak out. For example, I have a rule tied to my motion sensors in the living room. If motion is idle for some period of time (checked every second via cron), and any of the lights are on, it shuts them all off. The problem is that the rule keeps firing because it thinks that the lights are on when they aren’t.

Is there a way you can put a periodic sanity check in to make sure the items actually match what the hub believes and fix any that are not correct?

BobA · October 31, 2020, 4:54pm

When this happens, do the devices show up in the right state in the Lutron app? One of my friends with a Caseta systems was seeing a similar intermittent problem, but it seemed that in that case the hub itself was missing the updates, so there wasn’t much that could be done from the binding’s point of view.

I can look at adding some polling logic to the binding, but it will add a lot of complexity, so I’d rather not do it if it isn’t really necessary.

morph166955 · October 31, 2020, 6:22pm

I’ll check to see what the app thinks next time it happens. Would there be a way to create a switch channel that could be manually fired by a rule to just force a resync? Or just reset the entire connection/logic as if the binding just came online?

BobA · November 1, 2020, 6:26pm

Well, re-setting the connection wouldn’t help. I could update the thing handlers so that when a channel receives a REFRESH command it will re-query the bridge. Some of the newer ones already support this. But the better solution would be to create periodic polling jobs with some optional parameter to control them.

However if the problem is on the bridge side as I suspect, then none of that would really help, and it’s best not to do polling if it isn’t necessary. So we should probably wait to find out what is really going on.

guterm · November 2, 2020, 1:58am

Observing the same behavior, missing event from dimmer being switched on.
Checked on the Lutron app and you are right, the bridge is missing the update as well.
It’s very strange, cause I can reliably change the state of the dimmer from the app itself.
I’ll submit bug report to Lutron, will see if they come back with anything useful.

Frenchman · November 3, 2020, 1:41am

I tend to like moderate fade-up times and fairly long fade-down times on my dimmers, but everyone has a different opinion in it. Have fun arguing about it with your family!

Haha. My kids went off to college so it’s mostly me now, and my GF about 1/3 of the time. She doesn’t care. I can replace arguing with my family with indecision about “what’s best.” That will keep me busy .

I do feel though that what my regular Maestro do is perfect: pretty quick fade-up and fade-down, and the ability to long press to get more time before fade-down. I really wish Caseta had gone with that (and kept 7 levels of LEDs everyhere, and added LEDs to a version of the Pico keypad, …), but as you said, they may have been afraid of cannibalizing their higher end solutions.

morph166955 · November 16, 2020, 9:52pm

Finally remembered to catch this. Yes, the app believes the light changed when it didn’t. When I had this issue on the IP bridge, we introduced the delay option under the thing to slow down the messages. My theory, assuming that the bridge actually didn’t screw up, is that there was so much traffic on the Lutron RF side that the switch missed the signal. Not sure if they can fix that easily or not.

Can we (re)introduce the delay feature on the LEAP side to see if it clears this up?

BobA · November 17, 2020, 6:01pm

The leapbridge supports the same delay parameter as ipbridge, so you should be able to test it out now!

morph166955 · November 20, 2020, 1:15am

I’ll put it back in to see if it fixes anything.

Part 2. My bridges have been going offline random and not coming back online without a restart of OH. Not necessarily both at the same time. I attempted to update the logging config but it looks like logging config is different on OH3 now. If someone can give me the correct syntax I’d like to peel Lutron logs off to a different file to see if I can catch why these go offline.

morph166955 · November 21, 2020, 10:01pm

Just had time to finally look at the delay. Apparently I already had the delay parameter in the thing config. It’s set to 100 right now.

EDIT: Captured one of the lights not going off… This was part of about 20 lights being shut off at the same time. From what I can tell, the hub thinks that the lights are going off but they aren’t. I will say there was a definite delay in what happened when the lights went off. About half went off, 5-10 seconds went by, and then the other half went off minus this one light.

2020-11-22 12:24:29.345 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,35,1,0,0.25
2020-11-22 12:24:30.135 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/26/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-22 12:24:30.158 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/26/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"}}}}
2020-11-22 12:24:30.164 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/26/status/level"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"},"StatusAccuracy":"Good"}}}
2020-11-22 12:24:30.164 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 26 level: 0
2020-11-22 12:24:30.164 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 26 mapped to device id 35
2020-11-22 12:24:59.774 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,35,1,100,0.25
2020-11-22 12:24:59.775 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/26/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 100, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-22 12:24:59.796 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/26/status/level"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":100,"Zone":{"href":"/zone/26"},"StatusAccuracy":"Good"}}}
2020-11-22 12:24:59.797 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 26 level: 100
2020-11-22 12:24:59.797 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 26 mapped to device id 35
2020-11-22 12:24:59.799 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/26/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":100,"Zone":{"href":"/zone/26"}}}}
2020-11-22 12:25:01.244 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,35,1,0,0.25
2020-11-22 12:25:01.244 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/26/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-22 12:25:01.270 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/26/status/level"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"},"StatusAccuracy":"Good"}}}
2020-11-22 12:25:01.270 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 26 level: 0
2020-11-22 12:25:01.270 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 26 mapped to device id 35
2020-11-22 12:25:01.275 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/26/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"}}}}
2020-11-22 12:25:05.759 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,35,1,100,0.25
2020-11-22 12:25:05.759 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/26/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 100, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-22 12:25:05.786 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/26/status/level"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":100,"Zone":{"href":"/zone/26"},"StatusAccuracy":"Good"}}}
2020-11-22 12:25:05.787 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 26 level: 100
2020-11-22 12:25:05.787 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 26 mapped to device id 35
2020-11-22 12:25:05.789 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/26/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":100,"Zone":{"href":"/zone/26"}}}}
2020-11-22 12:25:08.921 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,35,1,0,0.25
2020-11-22 12:25:08.921 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/26/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-22 12:25:08.937 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/26/status/level"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"},"StatusAccuracy":"Good"}}}
2020-11-22 12:25:08.938 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 26 level: 0
2020-11-22 12:25:08.938 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 26 mapped to device id 35
2020-11-22 12:25:08.947 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/26/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/26/status","Level":0,"Zone":{"href":"/zone/26"}}}}

morph166955 · November 22, 2020, 1:37am

That didn’t take long. Both bridges went offline. When they came back, they were effectively static. Changes on the app don’t show up on OH. Commands don’t send. Nada. I’m worried we have some sort of exhaustion issue happening. Possibly related to the delay, not sure why. You may need to purge the queue out when the devices comes online to make sure there isn’t anything hanging out that is stale and old.

EDIT: Let me add some extra context I just noticed. My zwave motion sensors and rules could be causing this condition to happen. Effecitvely the rule says “if there has been no motion for X seconds, and any lights are on in that room, turn them off”. That runs via cron every second. Because the bridge was offline for some period of time, it looks like the status of the devices never updated so it kept trying to fire that rule off which would cause 4-5 lights to try to shut off every second. I’m updating my rules to not do this kind of flood anymore, but it semi-confirms that the queue could be causing the issue.

2020-11-21 16:27:01.578 [DEBUG] [n.internal.handler.LeapBridgeHandler] - End of input stream detected
2020-11-21 16:27:01.578 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 2
2020-11-21 16:27:01.579 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 3
2020-11-21 16:27:01.583 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 4
2020-11-21 16:27:01.583 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 5
2020-11-21 16:27:01.583 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 6
2020-11-21 16:27:01.584 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Message reader thread exiting
2020-11-21 16:27:01.584 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 9
2020-11-21 16:27:01.584 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 11
2020-11-21 16:27:01.584 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 7
2020-11-21 16:27:01.584 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10
2020-11-21 16:27:01.585 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 1
2020-11-21 16:27:01.585 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 8


2020-11-21 16:42:32.753 [DEBUG] [n.internal.handler.LeapBridgeHandler] - End of input stream detected
2020-11-21 16:42:32.754 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10
2020-11-21 16:42:32.756 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 11
2020-11-21 16:42:32.764 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 40
2020-11-21 16:42:32.764 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 39
2020-11-21 16:42:32.766 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 37
2020-11-21 16:42:32.767 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Message reader thread exiting
2020-11-21 16:42:32.767 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 16
2020-11-21 16:42:32.767 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 34
2020-11-21 16:42:32.767 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 35
2020-11-21 16:42:32.767 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 41


2020-11-21 17:59:50.941 [WARN ] [n.internal.handler.LeapBridgeHandler] - Communication error, will try to reconnect. Error: Connection or outbound has closed
2020-11-21 17:59:50.941 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 2
2020-11-21 17:59:50.942 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 3
2020-11-21 17:59:50.942 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 4
2020-11-21 17:59:50.942 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 5
2020-11-21 17:59:50.943 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 6
2020-11-21 17:59:50.943 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 17:59:50.956 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Attempting to reconnect to the bridge
2020-11-21 17:59:50.956 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 9
2020-11-21 17:59:50.956 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10
2020-11-21 17:59:50.956 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 11
2020-11-21 17:59:50.956 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 7
2020-11-21 17:59:50.956 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Disconnecting
2020-11-21 17:59:50.957 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 8
2020-11-21 17:59:50.957 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 1
2020-11-21 17:59:50.957 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 2
2020-11-21 17:59:50.957 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Opening SSL connection to 10.255.0.196:8081
2020-11-21 17:59:50.958 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 4
2020-11-21 17:59:50.958 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 5
2020-11-21 17:59:50.958 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 6
2020-11-21 17:59:50.958 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 9
2020-11-21 17:59:50.958 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10

Eventually they come back online and it looks like they try to send commands continously.

2020-11-21 18:01:38.050 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/44/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:38.150 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/23/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:38.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:01:38.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/33/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:38.951 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:01:38.953 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:01:38.953 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/3/commandprocessor"},"Body": {"Command": {"CommandType": "GoT
oFanSpeed","FanSpeedParameters": {"FanSpeed": "Low"}}}}
2020-11-21 18:01:38.955 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:01:39.049 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/44/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:39.150 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/23/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:39.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:01:39.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/33/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:39.950 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:01:39.952 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:01:39.952 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/3/commandprocessor"},"Body": {"Command": {"CommandType": "GoT
oFanSpeed","FanSpeedParameters": {"FanSpeed": "Low"}}}}
2020-11-21 18:01:39.953 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:01:40.050 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/44/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:40.150 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/23/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:40.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:01:40.949 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/33/commandprocessor"},"Body": {"Command": {"CommandType": "Go
ToDimmedLevel","DimmedLevelParameters": {"Level": 0, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}
2020-11-21 18:01:40.950 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25

They come back online but seem to start queueing up until finally all the log shows is…

2020-11-21 18:37:05.173 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:06.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:06.171 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:06.173 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:06.174 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:07.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:07.167 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:07.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:07.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:08.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:08.166 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:08.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:08.169 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:09.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:09.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:09.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:09.171 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:10.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:10.167 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:10.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:10.169 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:11.166 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:11.167 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:11.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:11.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:12.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:12.166 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:12.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:12.169 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:13.165 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:13.168 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:13.169 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:13.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:14.166 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:14.167 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25
2020-11-21 18:37:14.169 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,4,1,25
2020-11-21 18:37:14.170 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,31,1,0,0.25
2020-11-21 18:37:15.166 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,45,1,0,0.25
2020-11-21 18:37:15.167 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,57,1,0,0.25

BobA · November 25, 2020, 10:47pm

Hi. I’ve been pretty tied up lately, but I did take a fast look at this. The quick analysis is that I’m not sure what is going on. I’ll probably send you a PM over the weekend when I have more time with a request for some additional info.

morph166955 · November 30, 2020, 2:03am

Just FYI, no idea why this is happening but it still is. Both of my bridges went offline within a minute of each other and stayed offline for almost 45 minutes. Note that in this case, it never attempted to reconnect as it had done in the past. Perhaps I didn’t wait long enough, not sure. I needed my lights back for the end of the night so an OH restart was done.

I opened a bug to track https://github.com/openhab/openhab-addons/issues/9178

EDIT: I remembered to pull logs. It looks like my rules worked and didn’t try to fire any commands when the bridge went offline. Trace logs:

2020-11-29 19:15:04.599 [INFO ] [me.event.ThingStatusInfoChangedEvent] - Thing 'lutron:leapbridge:bridge2' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Connection lost
2020-11-29 19:15:04.666 [INFO ] [me.event.ThingStatusInfoChangedEvent] - Thing 'lutron:leapbridge:bridge1' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Connection lost

2020-11-29 19:11:13.367 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"MultipleOccupancyGroupStatus","StatusCode":"200 OK","Url":"/occupancygroup/status"},"Body":{"OccupancyGroupStatuses":[{"href":"/occupancygroup/13/status","OccupancyGroup":{"href":"/occupancygroup/13"},"OccupancyStatus":"Unoccupied"}]}}
2020-11-29 19:11:13.367 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - Received CommuniqueType: ReadResponse
2020-11-29 19:11:13.367 [TRACE] [rnal.protocol.leap.LeapMessageParser] - MessageBodyType: MultipleOccupancyGroupStatus
2020-11-29 19:11:13.367 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Parsing occupancy group status list
2020-11-29 19:11:13.367 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - OccupancyGroup: 13 Status: Unoccupied
2020-11-29 19:11:13.367 [TRACE] [n.internal.handler.LeapBridgeHandler] - Group 13 state update: Unoccupied
2020-11-29 19:11:13.389 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/24/status/level"},"Body":{"ZoneStatus":{"href":"/zone/24/status","Level":0,"SwitchedLevel":"Off","Zone":{"href":"/zone/24"},"StatusAccuracy":"Good"}}}
2020-11-29 19:11:13.389 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - Received CommuniqueType: ReadResponse
2020-11-29 19:11:13.389 [TRACE] [rnal.protocol.leap.LeapMessageParser] - MessageBodyType: OneZoneStatus
2020-11-29 19:11:13.389 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 24 level: 0
2020-11-29 19:11:13.389 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 24 mapped to device id 32
2020-11-29 19:15:04.599 [DEBUG] [n.internal.handler.LeapBridgeHandler] - End of input stream detected
2020-11-29 19:15:04.600 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 2
2020-11-29 19:15:04.600 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 3
2020-11-29 19:15:04.600 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 5
2020-11-29 19:15:04.600 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 4
2020-11-29 19:15:04.600 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 6
2020-11-29 19:15:04.600 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Message reader thread exiting
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 9
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 11
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 7
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 8
2020-11-29 19:15:04.601 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 1
2020-11-29 19:15:04.663 [DEBUG] [n.internal.handler.LeapBridgeHandler] - End of input stream detected
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 10
2020-11-29 19:15:04.664 [DEBUG] [n.internal.handler.LeapBridgeHandler] - Message reader thread exiting
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 11
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 40
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 39
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 37
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 16
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 34
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 35
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 41
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 36
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 23
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 29
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 30
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 32
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 31
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 45
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 57
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 47
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 49
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 50
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 51
2020-11-29 19:15:04.664 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 52
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 53
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 54
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 55
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 62
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 64
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 66
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 67
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 65
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 70
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 72
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 74
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 75
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 77
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 76
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 78
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 84
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 85
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 86
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 81
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 80
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 82
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 83
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 87
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 2
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 6
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 12
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 13
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 16
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 22
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 19
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 33
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 20
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 42
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 43
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 60
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 68
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 69
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 71
2020-11-29 19:15:04.666 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 79
2020-11-29 19:15:04.666 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 1
2020-11-29 19:15:04.665 [DEBUG] [utron.internal.handler.LutronHandler] - Bridge status changed to OFFLINE for lutron device handler 73
2020-11-29 19:16:27.503 [ERROR] [org.jupnp.transport.spi.StreamClient] - Request: HttpRequest[GET /capability HTTP/1.1]@629629cf failed
2020-11-29 19:26:24.409 [DEBUG] [ry.LutronMcastBridgeDiscoveryService] - Scanning for Lutron bridge devices using multicast

Boyett · February 21, 2021, 6:21pm

I am trying to figure out why I am not seeing the leapbridge thing in my inbox when trying to configure my caseta non pro hub. I have the keystore and certificates. I am thinking that I may have an old version of the binding that doesn’t have the experimental leapbridge.
I am still running openhab2.xxx.

BobA · February 21, 2021, 7:06pm

Hi Damion. Yes, the changes to support the LEAP protocol were only merged in to 3.0. At the time I made them only fixes were still going in to 2.x. You can try using this beta version that includes a jar built for OH 2.5.9, but I would really recommend upgrading to the 3.0.1 release instead, since I made a lot of code changes after that beta version.

Boyett · February 21, 2021, 8:29pm

Alright I will try and migrate to 3.0.1. I did finally get the binding installed. I was missing the serial binding which was causing the lutron binding to fail. Now I am having issues with the key file.

Status:offline error initializing keystore

BobA · February 21, 2021, 10:31pm

If you set the logging level for the binding (org.openhab.binding.lutron) to DEBUG you should see what the specific keystore error is.