[shelly] Support for Plus RGBW PM

[markus7017]

The Plus version of the RGBW2 is the RGBW PM

[fd0cwp]

Hi @markus7017,
I just bought such a device and did not have a look beforehand if OH supports it. 😔
Are there any news?
Could I use your changes in OH 4.1.1? If yes, I would be happy to test it. 😉
Otherwise, I have to search for another device.

[fd0cwp]

Hi @markus7017,

Meanwhile I installed OH 4.2.0. The device is shown but obviously not available in the database:

Or did I something wrong?

[fd0cwp]

Interesting is the error message which says that the IP address is not configured, but in the Thing Properties section, it is visible, correct and in browser accessible.
Unfortunately, I do not have the possibility to configure anything:

[fd0cwp]

Hi @markus7017,

I had a closer look at the issue. The problem is that the binding tries to access a URL (http:///settings) which is not available on the device:

2024-08-10 20:40:43.738 [DEBUG] [shelly.internal.ShellyHandlerFactory] - Shelly RGBW2 White Mode: Create new thing of type shelly:shellyrgbw2-white using ShellyLightHandler
2024-08-10 20:40:43.778 [DEBUG] [shelly.internal.ShellyHandlerFactory] - Thing handler for uid shelly:shellyrgbw2-white:e923c3495d added, total things = 6
2024-08-10 20:40:43.781 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellyrgbw2-white:e923c3495d' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2024-08-10 20:40:45.789 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: Using default userId admin from binding config
2024-08-10 20:40:45.790 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: Using default password from bindingConfig (userId=admin)
2024-08-10 20:40:45.791 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: updateInterval = 60s -> skipCount = 20
2024-08-10 20:40:45.791 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: Config: Device address=<IP-Address>, HTTP user/password=admin/***, update interval=60
2024-08-10 20:40:45.791 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: Start initializing for thing Shelly RGBW2 White Mode, type shellyrgbw2-white, IP address <IP-Address>, Gen2: false, CoIoT: false
2024-08-10 20:40:45.822 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyrgbw2-white-e923c3495d: HTTP GET http://<IP-Address>/shelly
2024-08-10 20:40:45.837 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyrgbw2-white-e923c3495d: HTTP Response 200: {"name":"Lichtband Küche","id":"shellyplusrgbwpm-a0a3b35c7a28","mac":"A0A3B35C7A28","slot":1,"model":"SNDC-0D4P10WW","gen":2,"fw_id":"20240625-122911/1.3.3-gbdfd9b3","ver":"1.3.3","app":"PlusRGBWPM","auth_en":false,"auth_domain":null,"profile":"light"}
2024-08-10 20:40:45.838 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyrgbw2-white-e923c3495d: HTTP GET **http://<IP-Address>/settings**
2024-08-10 20:40:45.853 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyrgbw2-white-e923c3495d: HTTP Response 404: Not Found
2024-08-10 20:40:45.854 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyrgbw2-white-e923c3495d: Unexpected API result: 404/Not Found
2024-08-10 20:40:45.793 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellyrgbw2-white:e923c3495d' changed from INITIALIZING to UNKNOWN (CONFIGURATION_PENDING): Initialisierung oder Gerät im Schlafmodus.
2024-08-10 20:40:45.860 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellyrgbw2-white:e923c3495d' changed from UNKNOWN (CONFIGURATION_PENDING): Initialisierung oder Gerät im Schlafmodus. to OFFLINE (COMMUNICATION_ERROR): Es trat ein unerwartetes Problem beim API-Zugriff auf. Überprüfen Sie die Logdatei für genauere Informationen.

Do you have an idea why the binding tries to access http:///settings?

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/shelly-binding/56862/4038

[fragment9]

Do you have an idea why the binding tries to access http:///settings?

No, but it would need to be http:///#/settings.. Anyone with a quick and dirty fix to change this in the addon?