Luton Caseta switch items receiving commands out of nowhere after last OH update

Dear community,

Happy New Year everybody!

I’ve been running a stable 5.0 OH system on Ubuntu, no issues. Today I updated to 5.1 and Lutron switches are going insane. Somehow OH generates commands out of thin air, flooding the system and actually turning lights on and off.

This is what I see in the log (repeating into infinity):

2026-01-02 12:49:32.697 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Laundry_Light' received command OFF (source: org.openhab.core.thing$lutron:switch:caseta:laundry:switchstatus)
2026-01-02 12:49:32.698 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Laundry_Light' predicted to become OFF
2026-01-02 12:49:32.700 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'Laundry_Light' updated to OFF
2026-01-02 12:49:32.748 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Laundry_Light' received command OFF (source: org.openhab.core.thing$lutron:switch:caseta:laundry:switchstatus)

If I go and turn the switch on manually, it turns back off!
There is not a single line in the rules that would use or modify this switch.

The switch is defined like this:

// luton.things
Bridge lutron:ipbridge:caseta "Lutron IP Access Point" @ "Equipment" [ ipAddress=IPADDRESSOFLUTRON] {
Thing switch laundry "Laundry" @ "Basement" [ integrationId=9 ]	
}

// lutron.items
Switch Laundry_Light "Laundry Light" (gBasement_Lights) ["Lighting"] {channel="lutron:switch:caseta:laundry:switchstatus"}

Update: the problem is only related to switches, other Lutron devices like dimmers, picos, and shades work fine. Debug messages from the Lutron binding are not super-informative, it just shows a flood of messages being sent:

2026-01-02 12:58:07.401 [DEBUG] [utron.internal.handler.SwitchHandler] - Initializing Switch handler for integration ID 9
2026-01-02 12:58:07.402 [DEBUG] [utron.internal.handler.SwitchHandler] - Initializing device state for Switch 9
2026-01-02 12:58:07.402 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Sending command ?OUTPUT,9,1
2026-01-02 12:58:07.411 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message GNET> ~OUTPUT,9,1,0.00
2026-01-02 12:58:07.414 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Sending command #OUTPUT,9,1,0
2026-01-02 12:58:07.475 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message GNET> GNET> ~OUTPUT,9,1,0.00
2026-01-02 12:58:07.478 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Sending command #OUTPUT,9,1,0
2026-01-02 12:58:07.499 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message ~OUTPUT,9,1,0.00
2026-01-02 12:58:07.502 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Sending command #OUTPUT,9,1,0
2026-01-02 12:58:07.548 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message GNET> ~OUTPUT,9,1,0.00

Please help!

Thanks to the new feature in OH 5.1 we can see where these consoles are coming from.

source: org.openhab.core.thing$lutron:switch:caseta:laundry:switchstatus

The command’s are coming from the binding itself. It seems like it’s reflecting the stateUpdate back to the Item as a command. But it shouldn’t do that and I’m not sure what you can do about it except filling an issue.

Updated, I filed an issue: [lutron] Caseta switch items receiving a flood of repeating commands out of nowhere after update to OH 5.1 · Issue #19952 · openhab/openhab-addons · GitHub