https://twitter.com/Frenck/status/1426906463407050755
Just wondering if this is something that actually got finished. If so, where is this feature hidden at?
Is there any particular reason you do not want to use the core Shelly integration?
It works very well and is local.
Glad to hear those remarks. I just assumed the ESPHome flavor of firmware would be the preferred method.
No, not at all.
I use many Shelly devices (including an EM and a 1PM) and they all work flawlwssly with the core integration. It is IoT class “Local Push” too (the best class).
All you have to do is make sure to set up CoIoT unicast in the 1st generation devices:
The only advantage with ESPHome is that you can run some more advanced automation on the device.
I don’t use twitter, so i can’t see first link, but i’l answer about “why use esphome and not original shelly ”: it’s not that it doesn’t work, it’s because it doesn’t work the way I want it to work. I flash all my shelly’s even before i connect them for the firsti time. Because i program FW my way. Using original FW you’re limited with function THEY decided to put in. Using esphome sky is the limit (or, should i say your programming skills…)
Just one of examples: shelly 2.5PM: it has 2 relays and only 1 button onboard. I use this button this way: one quick press:toggle relay1, two quick presses: toggle relay2. Ok, button is rarely used, but when you’re doing something on that device it’s usefull for testing. Also, button can be used for, say module reset at long-press but still works as toggle switch.
I also use led inside for connection monitor: even flashing: wifi:yes, ha:no; small flashes: ha connected; steady lit: no wifi, no ha.
Yes I did mention that.
If you don’t need to then there is no reason to flash the device.
1 Like