and do you plan to support
shelly pro 1 and pro 2?
thank you.
There's drivers for Shelly Pro 1, Pro 2 PM, Pro 3, and Pro 4PM. I'll get the other Pro devices posted here in a few minutes, it's really quick to add them at this point, since my main library code has everything they'll need already included.
1 Like
great. in my case, i have only the pro1 and pro2.
but on you current list of drivers, i can not see the Pro 1.
BTW and the Shelly Duo GU 10 ( white ) is supported?
New release on HPM, added support for:
Shelly 1 (gen 1)
Shelly Pro 1PM
Shelly Pro 2
Shelly Pro Dimmer 1PM
Shelly Pro Dimmer 2PM
Shelly RGBW2 (gen 1)
For the Shelly RGBW2, in both RGBW and White x4 modes, each mode needs a different driver, both drivers added. Don't swap between them on the fly, it'll cause issues. If you need to change modes, delete the device from Hubitat and add it using the other driver.
Added a driver for "Shelly Duo WW CW", it should work with both the E27 and GU10 version.
1 Like
Update on HPM: Added support for Shelly Pro EM
Thanks for all the updates. The external temp sensors on the Uni Plus, code etc has been solid.
thank you it. i have the Pro 1 ( only ). From your list, what should i use ?
Forget my question. I did not deleted just to other see my mistake.
when you lunch a new driver, we need to explicit refer that we need that driver to be add to therepository. It is not automatically add as part of all package.
thank you
Yes, all the drivers are marked as “not required” for HPM. So to get a newly released one you’ll need to run HPM and select the new driver to get it downloaded.
New release on HPM: Adds support for Shelly Pro 3EM400, including handling the switch add-on.
Another new version on HPM: Adds Shelly EM, Shelly 3EM support.
2 Likes
Hi
Any driver for Shelly 2pm gen 3?
The driver for the Gen 2 Shelly Plus 2PM will work with the Gen 3.
The only notable differences between the two are the virtual components, BTHome components, KNX, and Matter, none of which these drivers do anything with, since none of these things have a part in Hubitat controlling the Shelly device.
Both the Gen 2 and 3 have the same “skeleton” which is what the drivers handle: 1 cover when in cover mode, two inputs, and two switches when in switch mode.
Edit: On this note, I'll be doing some cleanup on these drivers, part of which will be to rename them so they're a bit more clear.
2 Likes
Hello! Thank you for these drivers! I'm using these with close to no issues for some time now and these are great! So many many thanks for your work!
I've now installed a Shelly Plus RGBW PM as a replacement for shelly RGBW2.
Fistly, even though I've installed the driver bundle via HPM, I don't see Shelly plus RGBW PM driver available... So I installed this one by hand via drivers code.
I can now see it, however when I add a virtual device and select this new driver, I can't see an IP Address...
I'm sure I'm doing something wrong, just don't know what 
Thanks for any help!
About Shelly Button 4 ( blu ).
I just add to my device list. but i have this error messagem:
dev:5612025-05-03 09:06:16.401
error
groovy.lang.MissingMethodException: No signature of method: user_driver_ShellyUSA_Shelly_Button_4__Blu__1428.push() is applicable for argument types: (java.math.BigDecimal) values: [4]
dev:5612025-05-03 09:06:09.150
error
groovy.lang.MissingMethodException: No signature of method: user_driver_ShellyUSA_Shelly_Button_4__Blu__1428.push() is applicable for argument types: (java.math.BigDecimal) values: [4]
i am doing something wrong ?
also for Shelly Button 1 ( blu ), i have this error messagem on "hold":
error
groovy.lang.MissingMethodException: No signature of method: user_driver_ShellyUSA_Shelly_Button_1__Blu__1024.hold() is applicable for argument types: (java.math.BigDecimal) values: [1]
Possible solutions: hold(java.lang.Integer), off(), on(), find(), close(), cToF(java.math.BigDecimal) (method hold)
the "pushed" and "double tap" action is working perfect. thank you for your effort on supporting this drivers.
with my GU10 ( shelly duo white ) it works well.
The only way I was able to replicate that was by using the "push" command on the device in Hubitat. If I press buttons on my physical Shelly Button 4 device I'm not seeing that.
Are you getting these errors from clicking on the Hubitat UI? Like here:
I'll put out an update to change the signature passed in from the helper app to the library, and change the library to match what the Hubitat UI is doing, so it doesn't do that anymore.
But you're not actually seeing these errors when you press buttons on the physical Shelly device, right?
That sounds like an HPM issue, and I'm guessing you're possibly missing the driver library. I'd try to get HPM sorted out first. I double-checked, and mine shows the Shelly Plus RGBW PM driver in the optional list of drivers.
If not, then there's a whole load of things you'll need to install manually. You need the driver, the library, and all of the various 'component' drivers, since that's what these drivers use to create the child devices. You technically only need the ones used by whichever particular driver you're loading, and likely the easiest way to find that out is to just click "configure()" and look for error level log messages for "${driverName} driver not found", with the name of the driver that's missing in the place of "driverName".
