Openhab Version 4.0.3 Openhabian Raspberry Pi 4B
Shelly binding installed from UI
Shelly Plus 2pm firmware version 1.0.3 in roller shutter mode
Description:
Fresh install of Openhab 4.0.3 (I run a longstanding 2.5.12 setup on a different pi and am preparing for a migration to Openhab 4 as well as introducing quite a few shelly plus devices in my setup). The binding discovers happily all my dimmer2 and switch25 devices but fails to discover a (pingable and connectable) plus25pm device on the same subnet and broadcast domain.
When I try to add it manually using the IP address I get the following debug log
2023-09-23 20:52:36.072 [DEBUG] [shelly.internal.ShellyHandlerFactory] - ShellyPro 2PM Roller: Create new thing of type shelly:shellypro2pm-roller using ShellyRelayHandler
2023-09-23 20:52:36.142 [DEBUG] [shelly.internal.ShellyHandlerFactory] - Thing handler for uid shelly:shellypro2pm-roller:dad78c9269 added, total things = 6
2023-09-23 20:52:36.146 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellypro2pm-roller:dad78c9269' changed from UNINITIALIZED to INITIALIZING
2023-09-23 20:52:38.151 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Using userId admin from bindingConfig
2023-09-23 20:52:38.152 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Device config: Device address=192.168.10.230, HTTP user/password=admin/***, update interval=60
2023-09-23 20:52:38.152 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Configured Events: Button: false, Switch (on/off): true, Push: true, Roller: true, Sensor: true, CoIoT: false, Enable AutoCoIoT: true
2023-09-23 20:52:38.153 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Start initializing for thing ShellyPro 2PM Roller, type shellypro2pm-roller, IP address 192.168.10.230, Gen2: true, CoIoT: false
2023-09-23 20:52:38.170 [DEBUG] [g.shelly.internal.api2.Shelly2ApiRpc] - shellypro2pm-roller-dad78c9269: Connect Rpc Socket (discovery = false)
2023-09-23 20:52:38.170 [DEBUG] [helly.internal.api2.Shelly2RpcSocket] - ShellyPro 2PM Roller: Connect WebSocket, URI=ws://192.168.10.230/rpc
2023-09-23 20:52:38.205 [DEBUG] [helly.internal.api2.Shelly2RpcSocket] - ShellyPro 2PM Roller: WebSocket connected /192.168.10.231:37560<-/192.168.10.230:80, Idle Timeout=2147483647
2023-09-23 20:52:38.248 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Unable to initialize, retrying later
2023-09-23 20:52:38.251 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Update status job started, interval=20*3=60sec.
2023-09-23 20:52:38.154 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellypro2pm-roller:dad78c9269' changed from INITIALIZING to UNKNOWN (CONFIGURATION_PENDING): Initializing or device in sleep mode.
60 seconds later it retries initialisation with the following debug
2023-09-23 20:53:37.254 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Status update triggered thing initialization
2023-09-23 20:53:37.255 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Start initializing for thing ShellyPro 2PM Roller, type shellypro2pm-roller, IP address 192.168.10.230, Gen2: true, CoIoT: false
2023-09-23 20:53:37.257 [DEBUG] [g.shelly.internal.api2.Shelly2ApiRpc] - shellypro2pm-roller-dad78c9269: Disconnect Rpc Socket on initialize
2023-09-23 20:53:37.258 [DEBUG] [helly.internal.api2.Shelly2RpcSocket] - ShellyPro 2PM Roller: Disconnecting WebSocket (/192.168.10.231:37560 -> /192.168.10.230:80)
2023-09-23 20:53:37.264 [DEBUG] [g.shelly.internal.api2.Shelly2ApiRpc] - shellypro2pm-roller-dad78c9269: WebSocket connection closed, status = 1006/Disconnected
2023-09-23 20:53:37.267 [DEBUG] [g.shelly.internal.api2.Shelly2ApiRpc] - shellypro2pm-roller-dad78c9269: Closing Rpc API (socket is disconnected, discovery=false)
2023-09-23 20:53:37.295 [DEBUG] [g.shelly.internal.api2.Shelly2ApiRpc] - shellypro2pm-roller-dad78c9269: Connect Rpc Socket (discovery = false)
2023-09-23 20:53:37.296 [DEBUG] [helly.internal.api2.Shelly2RpcSocket] - ShellyPro 2PM Roller: Connect WebSocket, URI=ws://192.168.10.230/rpc
2023-09-23 20:53:37.367 [DEBUG] [helly.internal.api2.Shelly2RpcSocket] - ShellyPro 2PM Roller: WebSocket connected /192.168.10.231:54052<-/192.168.10.230:80, Idle Timeout=2147483647
2023-09-23 20:53:37.392 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Unable to refresh status: Unable to update status
2023-09-23 20:53:37.397 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellypro2pm-roller-dad78c9269: Enabling channel cache (20 updates / 60s)
2023-09-23 20:53:37.267 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellypro2pm-roller:dad78c9269' changed from UNKNOWN (CONFIGURATION_PENDING): Initializing or device in sleep mode. to OFFLINE (COMMUNICATION_ERROR): Unexpected error: WebSocket connection closed abnormal
and the error keeps alternating between
(COMMUNICATION_ERROR): Unexpected error: WebSocket connection closed abnormal
and
(CONFIGURATION_PENDING): Initializing or device in sleep mode.
I can see it is doing an initial connect and getting the right response including discovering the plus sensor add on but then something goes sideways…
Stumped I’m afraid so casting to the wider community
Have lots of MQTT, Modbus, Z-Wave, Shell Gen-1 and other assorted things running but this one is failing me…
Thanks!
/A