Edge Shelly drivers for Gen1 and Gen2 Devices

I was just based on how UNI was created for me after adding it to their application as two separate devices, so it was then transferred to smarthings as two switches. I understood it to mean that the device can be used for two independent integrations. personally, I don’t see any added value in it, since it is one HW and has one IP address. I thought exactly that it would be difficult to program. it will certainly be simpler and better if it were one device and one could control two outputs and monitor the status of two inputs and see the values of all sensors on one screen

1 Like

So long as you have control of each relay output and can see the status of each input separately and use each individually within routines for me it wouldn’t matter.

Using Tasmota Edge I’ve configured it to work such that a single Uni has two devices (one for inputs and one for outputs) each with two components thereof.

Having said that, I think this would be the best option -
“if it were one device and one could control two outputs and monitor the status of two inputs and see the values of all sensors on one screen”.

1 Like

Coming soon…

1 Like

Any news on support for the H & T device?

GEN2 Device Driver Beta is now ready!

This is an early driver, so expect glitches. It should support the following GEN2 device types:

  • PlusPlug US (tested and verified!)
  • Plus 1, Plus 1PM
  • Pro 1, Pro 1PM
  • Pro 2

I’ve only been able to directly test the PlugPlug US; the rest I will be reliant on community members to test and report problems. I also do not have external sensor support yet.

For this first driver, anyone can try it, but I’ll only be able to figure out problems if you can provide logs using the CLI. So I’m really hoping at least a couple of you will be able to do that.

Differences from GEN1 driver
The Shelly folks have improved the design of these GEN2 devices making the API very modular. All of them share a small number of common components that all work the same across device types. Communications with these devices is through WebSockets, so I’m hoping this will be a more stable and reliable interface than GEN1, which relies on simple HTTP requests.

Another difference with this driver is that devices are discovered automatically, instead of having to create and configure the IP address for each device.

Available on my Test Channel: SmartThings. Add a little smartness to your things.
Driver: Shelly Gen2 Device Driver V1.0
Version: 2022-12-29T04:12:57.475328808


Once the driver is loaded to your hub from the channel, when you do an Add device / Scan for Nearby Devices, it will take about 40 seconds to perform a network discovery for your GEN2 devices. Be patient, the discovery process will continue even after the mobile app scan says it didn’t find any devices.

Devices will be automatically created for each device model found that is currently supported by the driver. An additional device labeled “Shelly Gen2 Device Creator” will also be created. This is for manual device creation only, in case discovery does not find your device. I’m hoping this manual creator will be unnecessary and if so I will eventually remove it. You can ignore it for now.

I look forward to your feedback!

Please do not post logs here. Send them to me in a direct message instead.


Probably next week sometime.

Shelly Plus 1 added works well. The on/off operation is noticeably quicker now

As you said the scan process seems to have failed at first as only a “Shelly gen2 device creator” appears. However a few seconds later the Gen 2 plus 1 appears.

Quick name icon and room change via edit and all is good.

Thank you :pray:


I confirm shelly plus1 works great. for this model, there is an addon module to which external sensors can be connected, if it were possible to configure this as well, it would be perfect. I will try to order one module for test



I definitely will be adding support for the addon external sensors. Let me know when/if you get one and you can help me test!

1 Like

ok, I’ll let you know when I have it available.

any progress with Shelly UNI?

Regarding the H&T device - we may have an issue with that one. I didn’t realize it is a battery-powered device, and like the Flood sensor it cannot be awaken via wifi to get updates. I ended up having to implement a separate MQTT-based driver for the Flood device and it might be best to do the same thing with the H&T. I don’t know if MQTT is an option for you or not, but let me know.

1 Like

Surprise: I got the UNI device support done today @stelka_stelka @Channelk @Chris_Gaddy

Please exercise the device inputs to make sure they are reflecting on the Controls screen. If you have external temp & humidity sensors I’ll also be interested in if they are showing up correctly.

Driver Version: 2022-12-30T00:22:29.614767416

Let me know how you make out.


I haven’t got anything else intergrated to smartthings using mqtt but I certainly could work that way and it does make sense to use a similar approach to the flood sensorh

1 Like

OK then if you can get an MQTT broker (Mosquitto usually) set up on your LAN and configure your H&T device to use MQTT, you don’t have to wait for me to do some testing to make sure you are seeing the messages flow. You can use the Mosquitto client to subscribe to topic shellies/# and you should start seeing these messages:

shellies/shellyht-<deviceid>/sensor/temperature: in °C or °F depending on configuration
shellies/shellyht-<deviceid>/sensor/humidity: RH in %
shellies/shellyht-<deviceid>/sensor/battery: battery level in %
shellies/shellyht-<deviceid>/sensor/error: if different from 0, there is an error with the sensor
shellies/shellyht-<deviceid>/sensor/act_reasons: list of reasons which woke up the device: battery, button, periodic, poweron, sensor, alarm
shellies/shellyht-<deviceid>/sensor/ext_power: true, if the device is usb powered

I can start retro-fitting the Flood driver for the H&T device.

1 Like

great, thank you ,
how do I add it? when I go through shelly device creator - UNI it says “not implemented” and under shelly gen2 creator I can’t find UNI.

Thanks for help

I don’t have a UNI but for other Gen 2 devices you just issue a scan for the add device screen. It will find it eventually just be patient

1 Like

thank you, it was already done, I had to remove and re-add shelly device creator. and it can already be added. so I’m going to test.

once again, thank you very much

I have one more question for you, I know you wrote here once that you don’t know actiontiles, I’m trying to understand how it works. I use actiontiles to display all devices and statuses on one tablet as a dashboard. I connected UNI shells with action tiles and not all the functionalities were transferred. only one relay and all 3 sensors were transferred as shown in the photo. I am trying to find out why the ADCS input was not transferred. I looked on the actiontiles website to see if the voltage measurement function is supported there and it should be supported. so I wondered if the ADCS input is defined as “voltage measurement” or just not in the format that actiontiles needs to read it.

this is probably how I have an idea that it should be transferred to actiontiles

Do you think that the ADCS input could be defined in such a format that actiontiles would read it?

I am also attaching a link to actiontiles

That’s terrific thanks!

Unfortunately I won’t be back home until March but will certainly test it out then. I’m surprised the Uni hasn’t got a bigger following actually as they have so many use cases, buy perhaps now they might.

The adcs value does use the stock voltageMeasurement capability. I’m just guessing, but perhaps ActionTiles doesn’t support multiple component devices. The adcs value in the Uni device is contained in the ‘adcs’ component, not the ‘main’ component (the default first component in any device). See if there is somewhere in ActionTiles that allows you to specify the component.

1 Like