Edge Shelly drivers for Gen1 and Gen2 Devices

Devices & Integrations Device Ideas
, , ,
980

@TAustin

My Shelly PM Mini Gen 3 devices stopped updating in ST tonight. Two things happened today. I believe you updated the driver and I updated the firmware on the units. I don’t know which update caused the problem.

I have had 2 PMs running for about 6 months and they worked great in ST with your driver until tonight. They are still working normally in both the Shelly app and in Home Assistant. I installed a 3rd one tonight. It was discovered with out any problems but all the values are “0” in ST. They have been that way for several hours. After the install and updates I discovered you also updated the driver.

The firmware update fixed a problem I was having HA. The problem was that they stopped functioning as Bluetooth proxies.

I have rebooted all 3 units via the Shelly app, power cycled 2 of the 3 units, rebooted my ST hub, clear the cache in the ST app, and force stopped the ST app. None of these things helped.

I have a 4th unit that I could install tomorrow, run logs during the install, and DM the logs to you.

EDIT: The Shelly PM Mini Gen 3 do not have Matter and don’t work with the official c2c integration.

981

Hi @TAustin , thanks for the recent update and your hard work!

​I’m trying to set up my Shelly 1 Mini Gen4. After your latest V1.8 update, the device is successfully discovered via “Scan Nearby”, but I cannot control it at all (commands time out or are ignored).

​I have tested it with Authentication both OFF and ON, so that doesn’t seem to be the issue.

Looking at the ST UI, I noticed it shows fields for “Voltage value reporting”, “Minimum Voltage”, and “Analog Value”, is it normal?

​I will share my device info in case it’s needed

For your reference, I pulled the exact details from the local API (/rpc/Shelly.GetDeviceInfo):

  • ​Model: S4SW-001X8EU

  • ​App: Mini1G4

  • ​Gen: 4

  • ​Firmware: 1.7.5

982

This device is compatible with Matter over WiFi.

Also possible to use this HTTP Devices driver

983

thanks for the suggestions!

​I am aware of the Matter compatibility, but unfortunately, the standard Matter implementation in SmartThings currently only exposes the main physical relay (On/Off). It doesn’t expose the separate logical input (button/switch events) needed to run the Shelly in Detached mode.

My specific goal is to keep my smart bulbs continuously powered (never cutting the physical AC power), while using the Shelly’s physical switch input to trigger a local ST routine to toggle the bulbs logically.

​I also looked into the HTTP Devices / Web Requestor driver, but I’d prefer to avoid setting up and maintaining manual Webhooks/Action URLs on the Shelly side.

TAustin’s dedicated Shelly Edge LAN driver handles the local inbound WebSocket connection perfectly out of the box, keeping everything 100% local.

984

You don’t need anything to Shelly.

I think that this Settings (HTTP Devices Switch Device) are operating also Shelly 1 Mini Gen4.

Screenshot20260429165703SmartThings
Screenshot20260429165703SmartThings1080×1591 143 KB

I use this with the Shelly Plug M Gen3.

985

I have a doubt, isn’t this configuration one sided hub to shelly?

If I phisically press the button it shouldn’t work right?

Or am I missing something?

If you check the previous conversation the user @BFS had the same problem as mine, but with a pm1 mini instead of the 1 mini, and he solved with Taustin driver.

986

Yes You can control Shelly relay from SmartThings

987

Hi @TAustin

I mean for this product, its also for covers but 4Gen

I just found this on AliExpress:

Shelly 2PM Gen4 Zigbee 2 Channel Smart Switch Matter Control Curtains Nlinds Power Metering Compatible Alexa Homekit Google Home

988

@TAustin

Update on my Shell PM Mini Gen 3s.

Today I added my 4th PM Mini, but I didn’t update the firmware. When I added it to SmartThings it was updating and working as expected.

So I checked the other 3 PMs and found them all working and updating. I updated the firmware on the 4th device and it is still working. So it was not a Firmware issue.

A couple minor quirks I have noticed:

  1. The display on tile alternates between saying connected and the actual wattage. I don’t remember seeing this in the past.

Screenshot_20260429-141928
Screenshot_20260429-141928438×279 36.9 KB

Screenshot_20260429-141839
Screenshot_20260429-141839422×272 32.4 KB

  1. There is only a genetic icon on the tile. The lighting bolt for power would be a good icon. This is NOT new.

  2. The Power Factor always reads “0” on the details page. I don’t know if this is new problem or I never noticed. FYI I don’t see Power Factor in the Shelly app or Home Assistant, so it may not exist.

So since things are working as expected I didn’t send you any logs. If want logs let me know.

989

Hey - Sorry to hear you were having problems. I wonder if it was related to the recent driver update, but that shouldn’t have (in theory!) affected your Gen3 device.

I believe the ‘Connected’ text is something that SmartThings controls; my driver doesn’t ever display that. It’s like it thinks the device is losing connection for some reason. I may need to see driver logs to see what may be causing this and to see if indeed the device connections keeps getting reset.

This is something I’d need to get more input from the community on. It seems that everyone has varying needs on what they want to see for the icon, depending on what they’re using the device for. There is a way make this a device preference which involves creating multiple device profiles for different device types, and letting the user pick which one they want. But it’s a very onerous thing to implement and manage for the developer, especially given the number of different Shelly devices there are, so I tend not to go down that path.

This is old knowledge and maybe is no longer true, but I had thought that Android app users had more flexibility than iOS in choosing device icons. But maybe we could get consensus of all PM-type devices to be energy meter device types?

I’m open to ideas…

The documentation says of this field: “Last measured power factor (shown if applicable)”. Maybe it’s not being reported by your device?

If you look in the Shelly app, can you see it there?

990

I could look at implementing the 2PM Gen4 device. It’s a bit more complex due to it’s multiple modes (switch and cover). Let me get back to you.

991

Something doesn’t sound right. You shouldn’t have voltage fields on that device.

Can you please open a browser tab and type in your Shelly IP address followed by ‘/status’? For example:

http://196.168.1.200/status

Post the results back here.

992

@TAustin

Updating: My 4 Shelly PM minis (gen 3) stopped updating again in the ST app earlier today. They are still working fine in the Shelly app and Home Assistant. No firmware or driver updates today. I rebooted the ST hub and it didn’t help.

Power Factor: I don’t see it listed anywhere in the Shelly app or in Home Assistant. It looks like something that it could be removed from the driver, but it is not a pressing issue.

Icon: There is NO option to change the icon in the ST app. These are weird devices. They do NOT have a relay, so there is no on/off capability. They only measure and report power, voltage, current, energy and frequency. So the only logical icon is the Lightning Bolt. Again not a pressing issue.

Alternating Wattage & Connected on tile: Since the devices are not updating they are displaying the last wattage read by the device. There is no alternating between watts and connected.

The lack of a relay is probably why they don’t work with Matter or the c2c integration.

I am currently out of town, so I can not produce logs. When I get back home I will get some logs and DM them to you.

993

@TAustin

Using the /status after my shelly IP give me a not found

Using /RPC/Shelly.getstatus give me this:



  "ble": {

  },
  "bthome": {

  },
  "cloud": {
    "connected": true
  },
  "input:0": {
    "id": 0,
    "state": true
  },
  "knx": {

  },
  "matter": {
    "num_fabrics": 0,
    "commissionable": false
  },
  "modbus": {

  },
  "mqtt": {
    "connected": false
  },
  "switch:0": {
    "id": 0,
    "source": "switch",
    "output": true,
    "temperature": {
      "tC": 64,
      "tF": 147.2
    }
  },
  "sys": {
    "mac": "7C2C676D05C8",
    "restart_required": false,
    "time": "04:27",
    "unixtime": 1777602424,
    "last_sync_ts": 1777601495,
    "uptime": 33595,
    "ram_size": 346380,
    "ram_free": 184380,
    "ram_min_free": 166868,
    "fs_size": 917504,
    "fs_free": 458752,
    "cfg_rev": 24,
    "kvs_rev": 0,
    "schedule_rev": 0,
    "webhook_rev": 0,
    "btrelay_rev": 0,
    "bthc_rev": 0,
    "available_updates": {
      "beta": {
        "version": "2.0.0-beta1"
      }
    },
    "alt": {
      "Mini1G4ZB": {
        "name": "Shelly Mini 1 Gen4",
        "desc": "Shelly Mini 1 Gen4 with Zigbee",
        "beta": {
          "version": "2.0.0-beta1",
          "build_id": "20260423-102551/2.0.0-beta1-g8c7700a"
        },
        "stable": {
          "version": "1.7.5",
          "build_id": "20260311-095841/1.7.5-g9979d16"
        }
      }
    },
    "reset_reason": 1,
    "utc_offset": 7200
  },
  "wifi": {
    "sta_ip": "192.168.50.125",
    "status": "got ip",
    "ssid": "Babiswifi_IoT",
    "bssid": "c6:fc:e7:32:f4:90",
    "rssi": -55,
    "sta_ip6": [
      "fe80::7e2c:67ff:fe6d:5c8",
      "fdfb:a13b:da4a:e7dd:7e2c:67ff:fe6d:5c8"
    ]
  },
  "ws": {
    "connected": false
  }
}
994

Can you please also do a /rpc/Sys.GetConfig?

Also - do you have the CLI installed and do you know how to get driver logs?

995

@TAustin yes no problem, here you go:

/rpc/Sys.GetConfig:
{
“device”: {
“name”: null,
“mac”: “7C2C676DXXXX”,
“fw_id”: “20260311-095905/1.7.5-g9979d16”,
“discoverable”: true,
“eco_mode”: false
},
“location”: {
“tz”: “Europe/Rome”,
“lat”: 41.8905,
“lon”: 12.5127
},
“debug”: {
“level”: 2,
“file_level”: null,
“mqtt”: {
“enable”: false
},
“websocket”: {
“enable”: false
},
“udp”: {
“addr”: null
}
},
“ui_data”: {
“device_revision”: “1-9”
},
“rpc_udp”: {
“dst_addr”: null,
“listen_port”: null
},
“sntp”: {
“server”: “time.cloudflare.com”
},
“cfg_rev”: 24
}

driver logs cli output:

2026-05-01T23:41:33.166024702+02:00 INFO Shelly Gen2/3 Device Driver V1.8 Shelly Gen2+ Device Driver v1.8.1 Started
2026-05-01T23:41:33.174572310+02:00 DEBUG Shelly Gen2/3 Device Driver V1.8 Device discovery invoked
2026-05-01T23:41:33.175058068+02:00 DEBUG Shelly Gen2/3 Device Driver V1.8 ********* Starting mDNS Scan #1…
2026-05-01T23:41:33.739022058+02:00 DEBUG Shelly Gen2/3 Device Driver V1.8 Discovered devices:
2026-05-01T23:41:33.739145837+02:00 DEBUG Shelly Gen2/3 Device Driver V1.8 shelly1minig4-7c2c676d05c8 fe80::7e2c:67ff:fe6d:5c8
2026-05-01T23:41:33.739440352+02:00 INFO Shelly Gen2/3 Device Driver V1.8 Creating Shelly device: shelly1minig4-7c2c676d05c8
2026-05-01T23:41:35.070598434+02:00 INFO Shelly Gen2/3 Device Driver V1.8 12a4d95f-0ba5-47bd-81fd-3d2e4e68576b: shelly1minig4-7c2c676d05c8> ADDED
2026-05-01T23:41:35.132210372+02:00 INFO Shelly Gen2/3 Device Driver V1.8 Initializing shelly1minig4-7c2c676d05c8 (1 Mini Gen4 1) at fe80::7e2c:67ff:fe6d:5c8
2026-05-01T23:41:35.236062260+02:00 INFO Shelly Gen2/3 Device Driver V1.8 1 Mini Gen4 1: WS Connect returned: nil, Address family for hostname not supported, nil
2026-05-01T23:41:35.236333663+02:00 ERROR Shelly Gen2/3 Device Driver V1.8 Could not connect: Address family for hostname not supported
2026-05-01T23:41:35.236602910+02:00 INFO Shelly Gen2/3 Device Driver V1.8 1 Mini Gen4 1: WS Connect will retry in 15 seconds
[… Error then loops every 15 seconds endlessly …]

I deleted and re-added the shelly for the purpose during the logging
hope it helps.

996

Thank-you. This is very helpful. And its also very interesting because one other person is seeing the exact same error. It looks like the network address being returned by SmartThings MDNS search library is returning an IPv6 address for the device, instead of the IPv4 address that it has previously returned. I don’t know why this has changed.

There is one other person (@Paul_Oliver) reporting this exact same issue, so something is going on that I’m going to have to investigate with SmartThings dev support. I may have you run a test version of the driver that displays details during discovery so we can verify what is going on. I’ll let you know.

I will get back to you, but it may not be until I hear back from SmartThings support early next week.

997

Yeah i noticed the ipv6 thing while watching the logs, so just as a test I tried disabling the ipv6 globally in my Asus router hoping the addressing would fallback to ipv4, sadly it didn’t work.

@TAustin just ping me when you need the test run, I’m glad to help.

998

Invited both you and Paul to a separate DM thread. Thank-you!

999

Hi help me