Shelly Device Handlers for Hubitat

You’re trying to paste it in the Apps Code section, need to go to the Drivers Code area.

1 Like

oh yes.thanks ,i did it in the driver now ,worked,but cannot see the Shelly addon contact.
iam useing Shelly one with external sensor (reed sensor).
what should i put the Tile on dashboard? relay or switch or what to see the external switch?


Near the top of the file there will be some lines that look like:

capability “Switch”
capability …

What do those say?

sorry .which file?
you mean the file which i paste in the driver?

the driver is working now ,but i couldnot see the contact on Dashboard.that what iam looking for,

the external switch stating well, but couldnot find on Dashboard..

Looks like the Switch and Power Meter templates should work…

1 Like

thanks . i found it by adding new tile holding same device name and choose contact sensor (tamplate).

am new to Hubitat ,so iam learning ,and this group is really great and helpful.
thank you again for your help and time spent. :+1: thebearmay

1 Like

it work perfectly,thanks a lot for your help.much aoppreciated.
I have another question please :
is there a way that i can add time delay to the refresh ,that refresh start after 5 second after action time done?

I added i3 support into my driver package, here: Vote for Shelly UNI - #16 by tomw . Note that I only supported the momentary type, not toggle. But that could be added if it is needed.

I don't have any i3 devices, but @nuno.licapinto did some testing with his. If anyone runs into issues with these please let me know.


@jihadd76 how did you get the Hubitat to recognize the external sensor?

I also copy pasted the Driver code over, and it has a lot more information than the built-in drivers, but I cannot seem to get it to show on HE.

I have the Shelly1 connected to Shelly Cloud, and the app shows the Open/Closed state of the sensor, I just can't get it out from the app.

1 Like

ok there is two Handlers, both written by Scott ( with many thanks for him for the great handlers he wrote) .
the second one diondp added the external switch only.
please go on this page scroll up till you find diondp. read the conversation please.

he added the external switch to Scott handler (which work as door on Shelly)
so "copy this driver "and paste in your driver code.

you should see in your new driver this : Line 144 attribute "ext_switch_state", "number"as shown in photo below

then it will appear in your device as ext _switch_state :0 or 1

then on Dashboard add it as a seperate Tile . door status

it will appear like that on your dashboard

Thanks for Scott for his efforts to write this drivers ,much appreciated.
and thanks for diondp who added the external switch .

Good luck.


hey tomw.
yes please,if you can add toggle to i3 will be great,i need this option whenever you have time to do this.

by the way,
i do like your shelly Uni driver ,i used it and happy with it. it is perfect.
thanks a lot for your time spent and efforts to write this drivers.much appreciated.


@diondp Have you tried putting this on Github and doing a PR against my code so I can merge it together? This would help a lot so I can keep track of any community changes to my code.

1 Like

what the benefits of useing Private Boolean in your Rule?
thanks in advanced

The message " OK, the door is closed" is only played when the door was to long open (in alarm).

1 Like

Sorry no... Im not that much into github function...

How do I do that?

@jihadd76 Thank you so much, that's what I was missing, diondp's additional code. I had come across it, but since I didn't find it on Github, I was afraid I was going to copy it wrong (first time gave me an error) and skipped it.

Have gone through the entire thread and would just like to add that HE is definitely a community-driven ecosystem, and everyone here scraping for answers but unable to contribute meaningfully for the most part (just like myself) should be thankful for the time and effort put here by its more technical members, and shouldn't take it for granted.

Most non-tech people are not fully aware of the work that has to be put into coding, no matter how small the project and think it's a sinch. It all goes back to the "make me a coffee" analogy.

So I would like to take the time to greatly thank @Evilborg for the effort and personal time put into these drivers, and am happy to see he was able to turn it into something more than just a driver for a couple of us knuckleheads to use. :slight_smile:

And I can't forget to also thank @diondp who stepped up to the occasion when needed and coded the external switch add-on for EvilBorg's already amazing driver (HE staff, just adopt it already!)

You're up there with the Cyanogen's and Koush's of the world, that make a whole platform better just out of your sheer willingness to help. That is to be lauded.


Do you have a github account? If not sign up for one and I'll walk you through it.

You are welcome...


i have a github account, what to do ?

Download the Hubitat app