Hi!
Moes ZT-SY-EU (zigbee 4 gang) and Sonoff SNZB-01P switches in pairing mode aren’t automatically discovered by Z2M, despite power cutting the whole house several times.
Several exact similar switches were all paired automatically in the past and work all fine using Home Assistant Green with a Connect ZBT-1 dongle (and blueprints). HA is up to date, from what I can tell. There are 21 zigbee router devices and 19 endpoints for now.
Have read several topics with no luck. Would be greatful if someone knew what could be checked, tested or done.
Switches, especially ones that were designed to work with Tuya/Smart Life, are fickle because they love to go to sleep, even when in pairing mode. Try hitting the switch/es of the device during pairing to keep it awake, if you haven’t already.
Hitting the “moon” looking like icon in Z2M (changes it into a “sun” looking like icon), as to “permit join all” mode is what I do, as well as hold the bottom left button of the Moes switch until all lights flash. Unfortunately, it’s after doing just that, that I came here. I also tried turning the house mains off for a minute (several times), without success.
Have tried hitting buttons while pairing, but no luck (and thanks for that tip too, @mmstano !). I’ve tested the battery, which I only just bought, @ShadowFist (but thank you so much for saying too).
Strangely, pairing the Sonoff Zigbee switch doesn’t work either. And I can’t even spot a Z2M ongoing traffic message about sniffing anything out, not even when the Connect ZBT-1 dongle only is an inch away from any of those Moes or Sonoff switches. And it won’t work from anywhere in the 3 rooms flat.
The switches packages do mention Zigbee capabilities. I don’t have a clue.
Thanks for clarifying. I had been mistaking this icon change and fidling for hours. You’re so helpful, and both switches types paired fine, very many Thanks, that did the pairing bit!
I’m however running into new trouble, as the Sonoff SNZB-01P doesn’t seem to have the “single action option”, unlike past ones which are still working fine.
There apparently is some change in Z2M updates, because of which HomeAssistant “legacy action sensors” are disabled by default. The Z2M front end settings workaround doesn’t seem to work for me.
Some advice to use MQTT device trigger instead of HA legacy_action_sensor…
Am trying to enable the legacy action sensors, but it doesn’t work using the Z2M frontend settings, which keep responding: “extension with name HommeAssistant already present”
I don’t know how to edit the Z2M yaml file using my smartphone, and can’t access HA using my laptop as I can’t remember my original account password. Any help is most welcome!
Instead of just waiting for help, tried several things one of which seems to work, but it may stop working won’t it if “legacy sensor actions” really do get depreciated ? Here it is anyway:
Didn’t work from the smartphone app, and didn’t recover my password to HA, so created a new user account using the smartphone app, giving it most rights. Logged into that new account using a laptop, then went to settings => automation and scenes before duplicating a similar (but working) switch into the parameters of which I modified the “device action” in yaml (three dots on the right), just pasting the yaml code of the switch that works, only changing the device id:
domain: mqtt
device_id: (the id is selected automatically when the switch is chosen through visual mode, before chosing to “modify in yaml”, using the three dots)
type: action
subtype: single
trigger: device
The new switch works fine. If someone knows if this workaround will not work forever, I’d be grateful to get advice for any sound future proof solutions, please.
It’ll work for however long you keep the device as-is. What that means… is the device_id is subject to change if, for example, you delete it and re-add it. That’s why most people prefer to use entity_id instead, when available, to future proof any changes that may happen to the device.
