Check the FAQs in the first post:
So it depends on whether your devices are Gen1 or Gen2+ models.
In case of the later you can contract Drenso (again, check the first post for how) with your request for support of your specific models.
Thanks for the reply.
I have a single wave i4 and two shelly wave mini’s. As far as I can gather, these devices released roughly alongside the Shelly gen 3 devices.
Hi all. I wanted to consolidate all my ZigBee devices under Shelly so I bought Gen4. I have Homey Pro 2019 (or what the year was before this new Gen). Is there anyone else that is using Shelly Gen4 in Zigbee that is satisfied with it? I first had incredibly hard time adding the device in Zigbee. IT would just hang, stop, with error “device stoped responding”.
Once I managed to add them after 100 retry whole ZigBee is become awfully unstable. I later tried testing only with 6 Shelly Gen4 on the ZigBee network (no other devices except Shelly) and for the firs time I saw Homey errors “ZigBee has been restored” error. What’s up with Shelly and Zigbee implementation?
Have you updated your Shelly Gen4 device to the latest v2.x.x firmware?
The original firmware many Gen4 devices shipped with (v1.9.x) had various Zigbee issues. The Zigbee part of the firmware seemed to be not yet mature enough. My Gen4 devices were basically unusable with that firmware in Zigbee mode (see also my earlier post on my observations).
I switched to WiFi/LAN mode and connected them to Homey via that route, similar like my older gen Shelly devices. The added value is that, in WiFi/LAN mode, the Shelly Control app exposes more sensors/capabilities to Homey then in Zigbee mode.
I had them upgraded to 2.x but still it’s barley usable. Barely. Tell me when it’s on Lan do you have tek on the same vlan as homey or you managed to separate them. I have ubiquiti, tried different vans with mDNS but doesn’t work.
I’m thinking about giving it a bit more time, 6 months or so by switching to Lan. If zigbee is not fixed I guess I’ll start looking for replacement.
Doesn’t sound like the issue is necessarily with Shelly, but more with your network becoming unstable. Could be that you simply have too many devices, and that these devices were the final push to let your network collapse.
In my case, they are on the same network as my Homey. Before I paired them with Homey, I assigned them a fixed/reserved IP and configured the Shelly device via its web portal. Then, when adding the device to Homey, Homey finds it instantly. I have several Gen2, Gen3 and Gen4 devices and have the same experience across them.
Oeps, wrong topic.
Yes indeed, I switch to Lan now as zigbee is horrible on Gen4 devices. I’m a bit disappointed for buying Shelly at all but ok, on Lan they do work quite fast. I was hoping I can have them isolated on different vlan from homey but in that case homey cannot find them. Once I added homey to same vlan it really did instantly detected them.
A well, I’ll have to live with it for now like this. Was hoping to have it on zigbee but it is what it it is.
I only now see this. No no, it’s completely new deployment. I had only 7-8 Shelly gen 4 devices at all on homey. With those couple of devices I saw for the first time that error zigbee has been recovered even after years of use of homey in different apartment.
Just to pair them to homey 2019 you could see this is not going well. I had to start pairing proces literally 15-20 times on some devices. I have only gen4, some 2pm, some 1pm and some 1pm mini all of which were on 2.x.x firmware.
I had some wifi issues with my Shelly 1PM Mini Gen 3 devices so I decided to enable the Wifi AP feature of nearby Shelly Power Strip 4 Gen4 for them.
I had no issues changing the connection details in the Shelly apps and in Home Assistant on iOS/Android however when I try to add them back using the Homey legacy or new apps I am unable to find them.
Could someone please advise how to get these added back to Homey as well after moving them behind the Wifi APs of the strips?
In the other two apps I was able to define them with the AP IP address and the port that is visible in the strip web interface (External IPv4):
I am having the same issue with my Shelly Plus 2 PM devices as well.
Hi,
I’d like to migrate a Shelly Plus 1PM (Gen2) with a Plus Add-On and an external temperature sensor from Shelly Legacy to Shelly Control on Homey Pro.
My current setup:
- Shelly Legacy 3.65.1 — relay control and external temperature readings work.
- Shelly Control 1.3.2 — I can see “Plus 1 – LAN”, but no dedicated “Plus 1PM – LAN” option.
- The temperature sensor is used in Flows controlling hot-water heating.
Is Plus 1PM currently supported, perhaps under another pairing option, or is support still planned? Will the Plus Add-On temperature sensor also be supported, and will it appear as a separate Homey device?
I can provide device details and diagnostics if needed.
Thanks!
I find the reports of battery level disturbing, as every % up and down is reported, sometimes within just 10 minutes.
Might suffice with 5% step changes I would assume. Or just make sure it doesn’t fluctuate nearly as much.
Only to report changes of 2% down and 3% up would help a lot!
My device is Ecowitt WS90 Weather station, but could apply to other devices as well I assume.
