Zigbee with gen4 Shelly work?

I've seen that some folks have gen4 Shelly devices in the wild that support zigbee. Has anyone tried them with Hubitat yet?

I'm super hopeful about gen4 zigbee support and am waiting to make a big device swap if they work.

@kkossev has tested a Shelly 1PM Gen4 and the switch works with the native driver. I'm not sure about the power monitoring feature.
I'll buy a Shelly 1 Gen4 (without power monitoring) today, but it will probably take more than a month to arrive.

Actually, my tests were not much successful.... :frowning:
I managed to pair Shelly Gen4 1PM just once :

Manufacturer: Shelly
Endpoint 01 endpointId: 01
Endpoint 01 idAsInt: 1
Endpoint 01 inClusters: 0000,0003,0004,0005,0006,0B04,0702
Endpoint 01 initialized: true
Endpoint 01 manufacturer: Shelly
Endpoint 01 model: 1PM
Endpoint 01 profileId: 0104
Endpoint 01 stage: 4
Endpoint EF application: unknown
Endpoint EF endpointId: EF
Endpoint EF idAsInt: 239
Endpoint EF inClusters: FC01,FC02
Endpoint EF initialized: true
Endpoint EF manufacturer: unknown
Endpoint EF model: unknown
Endpoint EF profileId: C001
Endpoint EF stage: 4

A minute later, the Zigbee connection was lost, and I could not pair it again (C-8 Pro).

Shelly Gen4 are using the standard ZCL clusters for reporting the power and energy, so I suppose it will work with the inbuilt HE drivers, providing if it pairs and stays connected. I don't know why I can not pair it anymore, tried with all my HE hubs (C8 Pro, C8, C7 ), tried to use all my pairing workarounds - no success. Update: a link to a complex and tricky pairing sequence post on the Shelly forum.

Switching between Matter and Zigbee interface is working (5 quick presses of the device button), but starting the Zigbee pairing (3 quick presses) worked just once. I will try again after a few days.

The good news is that Shelly Gen4 Matter mode is working well! - Power, Voltage, Amperage, Frequency, and PowerFactor readings are correct and not spammy. There is a problem with the accumulated energy readings, however.

I have just updated the Matter Advanced Bridge .

3 Likes

Thanks. Looks like we will need a wait a bit for them to get the firmware right for Zigbee. The US site either hasn't released them yet or is just out of stock.

I thought I picked up from the videos or help docs that you could have Zigbee and Wifi running at the same time. That would be an advantage for me if it's eventually true.

Secondarily, it's a shame that the X2 display is getting bad reviews. I was hopeful.

Yes, still seems too early, but this note from the QA team maybe helps. You can have Wifi and Zigbee at the same time as long we the wifi AP is not enabled.

After many tries, I managed to pair it to my C-8 Pro.

Using the Generic Zigbee Outlet driver, the power readings are off by a factor of 10.

fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006,0B04,0702",

Using the ThirdReality Power Meter Plug community driver :

So it works, but was really challenging to pair.

Maybe their docs would be useful for understanding the Zigbee clusters. The RPC cluster is interesting.

1 Like

Shelly Gen 4 works simultaneously via Zigbee (Tuya driver) and WiFi (tnx @dmitry.rozovik )!

3 Likes

Nice! thanks for confirming! Over time I'm sure we will see some full Zigbee drivers with RPC functionality.

Which Tuya driver is this? Is it built in or a download? I've just purchased some Gen4 Shelly 1 devices (non-pm) and I'm having some issues getting them working. They're detected okay (Device data IDs them as Shelly Mini1) but the driver it defaults to is Zemismart ZigBee Wall Switch Multi-Gang...have tried generic Zigbee switch and ShellyPlus Generic but neither seem to work.

@dmitry.rozovik , the gen4 devices are not listed under "Currently driver is expected to support...." , Is the list incomplete or is it an coincident the driver is working?

@dmitry.rozovik, or mayby your driver is working for Gen 2,3 an 4? :slight_smile:
Comparison of Shelly Gen 1, Gen 2, Gen 3 and Gen 4 Devices :

The list is mainly consists of devices used as a base for the implemenation. The driver is not focusing on specific devices but on device components. Gen2+ devices expose a set of component instances responsible for some subset of features. As long as component is supported, the related fetures will work. Gen4 devices follow the same Gen2+ API and thus are supported.

Some new specific componnets might be required to add (for more new featuers). But the total set does not seem to be changed at the moment. Components that are currently WIP (I'm waiting for a device to get at hand to test and finilize) are 'cct', 'rgb', 'rgbw'

All the documented componets can be fount here Welcome! | Shelly Technical Documentation
Not all of them are implemented by driver as not all of them have practical use.

1 Like

Thanks for your feedback. Wouldn't it be useful to add a note in the description of the driver at the top, indicating that Gen3 and Gen4 are also supported, as I was initially unaware of this?

Seems like an edgy comment to people that are contributing their personal time. While what you are asking is logical it's maybe unfriendly. Perhaps it's a language issue.

Gen4 devices are brand new. It's OK to assume things will get documented and supported in good time.

It does make sense to update a device list comment in a more generic way as it might confuse people. I'll edit it alongside with other changes. Due to the driver implementation approach and the same API Gen3 and Gen4 were supported right from their release (though few new components had to be added)

2 Likes

Of course this thread or topic is about Zigbee control.

The Shelly switches Gen4 (and now also Gen3 with the latest Shelly firmware) should work via Zigbee in HE using the inbuilt stock 'Generic Zigbee Switch' drivers. I am using this custom driver because of the power and energy scale adjustments.

With Debug logging turned on, do you see anything in the live logs when you turn the Shelly switch module on and off from the physical switch? Most probably, your device has left the Zigbee network ... Try pairing it again.