Unfortunately this will no longer be possible with the mg21 chip used in the blue switches. See Eric’s post linked below:

https://community.inovelli.com/t/zigbee-matter-motion-switch-project-linus-blue-series/10904/439?u=quaffs.cherub_0t

I started with ZHA, but moved to Z2M because there was an automation blueprint I needed that was only coded for z2m.

Gotta say, I’m a much bigger fan of the z2m interface. There’s nothing wrong with ZHA but unless something major changes, I don’t see the need to ever switch back.

RatGDO can do this without the need for a magnetic switch. It’s a simple ESP32 board with easy-to-terminate wire terminals. It also lets you control the lights on your opener, see the current status of the door, and even open the door to an exact in-between position (if your door supports it).

You can program your own ESP32 if you like, or buy one from the guy that made it directly for ~$40.

Still - props to you for making your own solution! I know it’s extra satisfying when you can homebrew your own smart home solutions from scratch - just wanted to share another solution for people who don’t have the same skills.

I had something similar (although probably unrelated) happen last week. All of a sudden my router went offline and nothing was getting an internet connection. Sonoff coordinator lost connection with all zigbee devices went unavailable at the same time. Tried rebooting my home assistant pc, router, unplugging sonoff antenna, switching Ethernet ports, etc without luck.

Power cycling my Ethernet switches fixed it immediately. No idea why that did the trick. This has never happened before. I’m on Verizon fios if that matters.

Posting here in case it helps someone identify a common thread/root cause for OP and me, because I thought it was bizarre that an Ethernet switch would ever need to be power cycled!

Thanks for confirming you had no issues (along with everyone else’s responses!). I took the plunge and updated yesterday and so far no issues apart from my inovelli switch triggers still missing. Luckily someone made an automation blueprint that circumvents this issue but it would still be nice to have that back! And to be fair, idk if that’s an MQTT issue or an issue with the 2.15 firmware on the switch.

Seems like a big update - do most Z2M updates include this many fixes/additions? I’m new to Z2M and am hesitant about updating unless I see a fix that will directly affect me positively.

Can anyone here report if they’re having any issues after updating? Looking at the comments, a number of people are reporting their devices not working shortly after updating, but idk if10 or so people posting is a large or small percentage of the user base.

I looked this up a while back. Someone wrote code to try to replicate it in homeassistant on their forums. If I recall correctly, it didn’t work quite as well as the hue version but I haven’t have a chance/reason to try it yet. Maybe someday soon.