I was having issue with zigbee pairing too. and tried switching to eco-mode which was a big mistake…instantly lost all connection and had to reset a couple of times to disable eco-mode and repair.
Thanks! I wrongly assumed that the more recent official firmware superseded the older beta. ZHA picked it up on zigbee correctly with 1.7 beta firmware. It didn’t pick up the sensor data for the addon using zigbee (temp and humiditiy) - I’ll stick to wifi for now (which is working fine). I don’t think Shelly should be advertising these as zigbee yet while they are still in beta. I bought the gen 4 with the addon because the Shelly website says it’s zigbee capable and I want the zibee mesh, it’s clearly not ready yet as per this thread, and is frustrating to have bought the addon if its not going to be zigbee supported. Hopefully this all gets sorted soon with an update.
2 Likes
I fully agree with that!
1 Like
For full support in Home Assistant’s native Zigbee Home Automation integration (i.e. Home Assistant’s own built-in Zigbee gateway) developers might need to create some ZHA Device Handlers (a.k.a. zha-quirks) or ever make a few changes to the upstream zha and zigpy libraries for Shelly Zigbee devices to expose custom features and fully work properly out-of-the-box nativly via the ZHA integration if those devices use custom Zigbee clusters and attributes instead of fully following standard Zigbee. Without that they probably only expose basic attributes that are standard. For more information see more about that here where you can post feedback too:
And
PS: For reference and more background information on what custom device handlers (zha-quirks) do for Zigbee devices with non-standard clusters and attributes in ZHA read this:
For reference, Shelly (the company) has now joined the ”Works with Home Assistant” (WWHA) partner certification program but so far they have only certified their Z-Wave devices and there is unfortunatly no mention if certification for Zigbee devices is also planned or not:
FYI, as I understand it, the agrement guidelines for that ”Works with Home Assistant” partner certification program stipulate that the company wanting to certify Zigbee devices for WWHA is more or less required to provide standard Zigbee OTA firmware updates nativly via Home Assistant’s built-in ZHA integration for certified Zigbee devices for standaized sustainability with support for local updates, and the devices themself also needs to have Zigbee CSA Certification as well.
Quote:
Available to access firmware updates directly in Home Assistant
Ideally, all devices should be able to access over-the-air (OTA) firmware updates from within our system. If this isn’t possible, you must provide a way to alert users about firmware updates.
1 Like
@Hedda It’s not the HA-integration that is limited per se. It’s more that the Zigbee functionality of the Shelly devices themselves is limited. Especially when compared to the extensive functionality that we’re used to from Shelly devices.
2 Likes
I was trying to get the Shelly 2PM Gen4 working as standard two outputs using the Zigbee and Z2M. When I connected I managed to control the outputs, but it was in Cover mode… i want it in two outputs mode, to control two lights… so I connected via Shelly App (WiFi), changed to two outputs, and disabled WiFi and connected again via Z2M… bus is still displaying as Cover mode… so I have no Idea how to do that… I prefer the Zigbee over WiFi, but I don’t want in this mode… any Ideas ?? Thanks.
Support for switching from cover to switch mode was added 5 days ago in the latest Z2M 2.6.1 release. Make sure your Z2M instance is updated.
EDIT: you might actually want to hold off updating until next month. There’s an issue with the state of the second output, and it seems the fix will rename your entities.
Did you try changing the mode via Shelly’s web interface and then re-adding the device to your Zigbee network?
Similar to a number of people here, I had challenges adding a Shelly device (1 PM Mini Gen4) to zigbee2mqtt. But, it is now connected.
On the Shelly device, I looked at the diagnostics log while the device was trying to join the network. The device was trying to connect, but failed. The device is reporting ‘shelly_zigbee.cpp:187 Network steering was not successful (status: ESP_FAIL)’.
Looking at some other forums on ESP and Zigbee and this error, I found the following. At first, I thought the messaged meant I had hardware issues with the ESP processing unit. A couple of times it was however linked to signal strength.
I was pretty sure that this wouldn’t work, but tried it anyway. I installed the device temporarily 0.5m from the coordinator/stick. Put zigbee2mqtt into ‘Permit Join’. Started the Shelly device, with diagnostics running. The Shelly device was added to the network in the 3rd automated attempt of joining. It is recognized and the relay is working.
Then I moved the device back to its original location. Started the device and looked at the output of relevant systems. It is stil connected and working well.
I can only explain this by saying the that Shelly might not be able to join through a router and only through the coordinator?
I had a similar experience with a new Shelly 2PM Gen4 that I tried adding to my Zigbee network. Didn’t try bringing it closer to the coordinator. That will be quite a challenge, given that the 2PM is stuffed away in a junction box behind a light switch… Maybe I should just hope that Shelly will fix this in a future firmware update.
Bringing my Shelly 2PM closer to my coordinator was not something I was looking forward to. The junction box it is in is just big enough to fit a Shelly and a couple of wires. I had a hard time squeezing it in last time. Getting it out and knowing it had to get in again eventually was not a great prospect. So I decided to give it another go while keeping it installed in the junction box. I once again double-checked all settings and this time I noticed that Bluetooth was turned on. But I don’t need BT. So I turned it off. Apparently, that was the magic trick, because after that it successfully paired on the first try!
4 Likes
I have two of these and added them via ZHA. All was sweet for a week. Now one has gone offline. What do I do? This is a PITA because they were installed by an electrician and are behind a wall plate controlling a lighting circuit. Please no “it’s yr zigbee network” or 'it’s not close enough to another zigbee router". Its less than 2 meters away from a hardwired very stable zigbee repeater… I have a 72 Zigbee mesh set up in less than 200sq meters…Zigbee has been around a decade (or more) … I could go on… enough already. This device needs to be 100% Zigbee stable… 
I’ve added the one that dropped off Zigbee to wifi. Why isn’t there a way in the Shelly Firmware to enter the device into Zigbee discovery mode?..edit… there doesn’t seem to be in the app… but I have found the Zigbee setting in the webGUI… Connection status… “steering”…? hit the pairing button…can’t add the zigbee device … hangs… so frustrating… for a fixed wired electrical device this is not Zigbee ready… not IMO… well not unless someone can help me out here… so so frustration COME ON SHELLY… you can’t advertise this as Zigbee ready unless it’s rock SOLID ready… I have 2 of these …one is no problem and the other is just plain flakey… it joins… works for like a minute… drops off the Zigbee network… 
That sounds like a really frustrating experience! Did you make sure to turn OFF bluetooth? In my case that solved my issues and after turning it off, I was able to pair it without problems, just with the pair option in the Web GUI. (I installed the Shelly myself, so I could remove the cover and push the physical button, but that’s a lot of hassle, and luckily, it was not needed.)