HTTP GET bug in 2.5.1.142 (and .143) breaks Shelly rgbw2 driver

[bendgilbert]

After upgrading my C-8 hub to version 2.5.1.142, all the command functionality in my Shelly rgbw2 driver stopped working. I am unable to turn the switch on or off, change the color, etc. These commands are sent to the Shelly device via standard HTTP requests - the IP address of the device is registered in a preference.

After seeing several similar topics in this forum, and seeing some HTTP fixes in the release notes, I tried upgrading to 2.5.1.143. However the problem still persists.

I have downgraded back to 2.5.0.136 and the driver is now working properly again.

In the logs, the commands in this driver are all working via a standard HTTP request. In 142 and 143, the request always fails with a 404 error, as shown here:

• Calling /color/0?turn=off

• something went wrong: com.hubitat.hub.executor.helpers.ExecutorHttpResponseException: status code: 404, reason phrase: Not Found

If I manually copy the exact URL shown in the log, and execute it in the browser against my Shelly device (which should just be a standard GET request), the command works as expected.

In this case, I am NOT using any login/password authentication on my request. However, I did try setting that up and the problem still occurs.

[gopher.ny]

Checking.

[BrunoVoeten]

similar issue with a shelly relay 2.5, acting as a rolleshutter since my latest update

Shelly Device Handlers for Hubitat

Allterco Robotics is pleased to announce that we've been granted transfer of copyright for the popular Shelly device handlers for Hubitat Elevation authored by Scott Grayban: This public repository hosts the latest editions of the device handlers, including several released here for the first time. If you're using older copies of any of these, we recommend you update in order to maintain the version check feature's functionality. These device handlers are freely available under the Apache 2…

this is the driver Shelly2-as-Roller-Shutter.groovy

[BrunoVoeten]

Hi @gopher.ny , is this issue still on the radar or should we look for an other sollution? Problem still exists on 2.5.1.147

[gopher.ny]

Please check 2.5.1.152, just released to the general public. It has what should be a likely fix.

[BrunoVoeten]

Hi @gopher.ny still not OK

Hope those log's can help:-)

this is when I close to position 80

This when I do a poll (don't know if it was supported)

this when I do a refresh

This is when I set level 80

When I close

When I use the shelly app to change the position, the status is updated in Hubitat. This is to position 90 using the Shelly app

[gopher.ny]

This is helpful, thank you. Can you send me a link to the driver code as well?

[BrunoVoeten]

Hi @gopher.ny , if you scroll up to the third message in this post you can find the link(s), thx for looking at the issue​

[bendgilbert]

I can confirm that my problem (using the Shelly RGBW2) is still not fixed after upgrading to 2.5.1.152. The same issue occurs with the 404 error from the driver.

Let me know if any logs would help.

[user7053]

Same issue for me with shelly 1 plus devices since updating the last 2 releases. My shelly devices stop working the only fix seems to be to rollback to a previous release.

dev:592026-08-14 8:38:53.476 pm

error

something went wrong: com.hubitat.hub.executor.helpers.ExecutorHttpResponseException: status code: 404, reason phrase: Not Found

[jon.d.tyler]

My Shelly 1's have also stopped working since I updated although my 2 dimmer 2s are still working ok at the moment.

I've just updated to .152 and I'm still having the same problem.

[gopher.ny]

On it. Next build.