Our driver uses the published shelly api to set the action links on the device.
I will setup one of these and verify that I can replicate the issue, as well as check the api calls are still valid (I mean they must be since as you say these work on older shelly firmware)
2 Likes
Unfortunately even installing the suggested firmware version does'nt allow my shelly 2.5 to work properly in a dashboard.
In my case, after configuration of the device in Hubitat the URL action links are empty in the Shelly
Can you check?
Maybe the issue where I am pointing to is not the same as yours.
@roberto, If was you, this is what I should try
- delete the device in Hubitat
- rollback of the Shelly firmware to 1.7.0
- factory reset of the shelly & reinstall it in the Shelly app
- add the device in Hubitat again, hit the save preference till you see the 2 channels
- check if the 5 action links are filled in for both channels in your Shelly device
- test ON/OFF in your 2 child devices and see if the status is changing (without refresh)
- If this works, create a new dashboard and add the 2 devices to test
@mike.maxwell, unless my memory is deceiving me, it looks like they fairly significantly changed their APIs for setting action URLs. They now require multiple data attributes and are at a settings/actions URI.
I would have expected them to maintain backwards compatibility, but... 
1 Like
For Shelly 1 and Shelly 2.5 there is no need to rollback the firmware.
The IO/URL actions are webhooks, instead of rolling back the firmware simply manually update these webhooks.
Hubitat uses the following patterns for the webhooks:
http://ip_address:39501/device_type/switch_id/action
ip_address: IP for your hubitat
39501: port used by my hubitat for these callbacks. I am guessing it's the same for everyone, but if it does not work check the URL Actions for a working switch to confirm.
device_type: either "button" or "switch"
switch_id: always 0 for Shelly 1, but maps to the switch number for Shelly 2.5 (0 or 1)
action: see below
On your Shelly 1 built-in URL Actions screen:
Button Switched On URL
Left blank
Button Switched Off URL
http://[ip_address]:39501/button/0/released/
Button Long Press URL
http://[ip_address]:39501/button/0/held/
Button Short Pressed URL
http://[ip_address]:39501/button/0/pushed/
Output Switched On URL
http://[ip_address]:39501/switch/0/on/
Output Switched Off URL
http://[ip_address]:39501/switch/0/off/
For Shelly 2.5 you enter the above for "Switch 0" and then change all the zeros for ones when entering "Switch 1" actions.
The button long and short press actions are only for momentary switches.
If you have toggle switches then these two actions are not needed.
Don't forget to check the "Enabled" box, and click "Save" for each individual action.
I tested on Shelly 1 and Shelly 2.5 devices. Everything worked as expected.
Hopefully Hubitat fixes this in a future update.
5 Likes
Ok, your right, but I think a rollback wil make it easier/faster.
The button type is not updated to when you press "save preference"
1 Like
Hi All,
i am having the issue with a shelly 1 with new firmware, switch does not update status unless you press refresh in device page, i am trying to roll back firmware as suggest but with no luck,
all i get is this
"{"status":"updating","has_update":false,"new_version":"","old_version":"20201124-091217/v1.9.0@57ac4ad8"}" showing in webpage,
am I doing something wrong?
i also tried adding those urls as dongood said but no luck either
i have mutiple shelly 1's and shelly dimmer 2's but i only have one that is having the issue for some reason
maybe you can try to factory reset the shelly 1 first and then try to update...
Thank you Bruno. Unfortunately it didn't work for me. Asap I'll dismiss my Shelly's and will install some zigbee switch
1 Like
Hi all,
I managed to roll back the firmware. Had to enable to the cloud connection on the device which I had disabled once the firmware was rolled back it started working again.
1 Like
Hi all,
Here's some more feedback:
Setting http://ip_address:39501/device_type/switch_id/action on the shellies manually 'almost works' for me.
The effect I see is on the hubitat child device, status changes but instead of "on" or "off" it's set to "on http" and/or "off http".
Easy and dirty fix, I guess, would be fore the Hubitat shelly drivers to accept "on http" as a valid value for "on".
Can't test if this also happens as I press the physical shelly button (SW), will test tomorrow and revert.
Cheers!
I just installed two new Shelly 2.5 switches. Both arrived with the latest firmware already installed.
tldr - Hubitat may have fixed the issue. See my Steps below.
I created the virtual device in HE per normal.
Using the built-in web admin screens, for "Channel 1" for the first Shelly 2.5 I went ahead and created the webhook entries as I described above. I then clicked the Shelly logo on the admin screen to go back to the home page, then selected Channel 2. Channel 2 already had the correct settings. I had omitted the Long and Short press URLs on Channel 1, but when I checked they were set as well.
For the second Shelly 2.5 I paid closer attention.
Steps
- Install the Shelly 2.5
- Using the built-in web interface set your static IP, username/password, etc.
- Check firmware to confirm the 20201217... version.
- Reboot Shelly to update the assigned IP address
- In HE add the virtual device.
- Back on the Shelly web UI, check to see if the Action URLs are set.
- If not set, click on the Shelly logo to launch the home screen, this appears to reset the admin site.
- Action URLs were now correctly set.
Firmware
Shelly 2.5: 20191217-074901/1047...
HE: 2.2.4.158 on C-5 Hardware
If it is correct what you say this is probably the reason it is working, we are 2020
If your firmware contains 2019 it is old firmware that works correct.
This is what I see in my shelly 2.5 right now:
Even with the BETA software it is still not working for me
My estimation: the problem is still there
I guess this is the issue:
Yep, definitely still not working, I've installed 6+ Shelly 2.5 just yesterday, the bug is still there.
As an early enthusiast of the Shelly products, now I'am really disapponted, both by the devices same as the customer management.
I want to substitute them all as soon as I find equivalent decent zigbee products
Did the workaround works for you? (downgrade to the previous Shelly firmware and config your Hubitat device, afterward you can update the shelly firmware again.)
Sorry to hear this, my experience is rather positive (I only have the relay's, 25+, they all work as expected)
Thank Bruno. They worked until few months ago. But even resetting and using a previous firmware version they are erratic.
I'm using them not connected to cloud.
Looking for small zigbee switch with EU full certifications
Sorry guys, I had a brain fart.
When I attempted to update my firmware the interface said I was already on the latest and I made the mistake of assuming, even though it was as plain as day that I was on a 2019 firmware.
One of the two devices still says it's on the latest firmware, time for me to research how to force the update.
1 Like
