Trigger: Unknown trigger (after extended power outage); can't get them to appear

Hey guys,

I recently came home from a vacation which involved a power outage that took place a few weeks back. Now, all of the Inovelli Blue switches we have installed aren’t working because Home Assistant can’t see the action triggers (up single, config double, etc).

I’ve tried the usual “press all of the action combos and check if they show up” but they do not.

I’ve tried running ‘Reconfigure’ on a few but that didn’t help. I’ve also tried restoring to a backup and that doesn’t help either.

Any other ideas?

image

After pulling the air gap and taking as many actions on the switch as is reasonable, I managed to get only config_held and config_release to appear.

image

The rest don’t seem to want to come back.

After multiple restores, it eventually worked…

Anything that could be done to improve this process?

After updating to the latest Home Assistant Core, the same issue appeared rendering all of the switches unusable.

I’m currently trying to restore backup after backup in hopes that it fixes itself but so far nothing.

Anyone else ever run into this?

[edit] Once again, after several restores eventually it started working again – very annoying though.

I have not run into this, are you using ZHA or Z2M?

I’m running Z2M.

You could try using @rohan’s blueprint he shared here or alternatively I saw this one referenced as well in a different thread.

The main difference between the blueprints (and the reason I built mine) is that mine doesn’t depend on device actions being available (since it listens to MQTT directly) not does it require turning on the legacy sensor entity in Z2M. It also can be used for multiple switches in the same automation because of that.

1 Like

I’ll give it a try.

Unrelated but can your blueprint be updated to expose a “initial button press” (triggering on press, not on release)? It’s something I’ve been asking for for a long time but am not confident we’ll see it in the actions list anytime soon.

I’m not aware of the switch reporting that currently. Until it does, the blueprint won’t be able to support that.

Yeah that was my guess. I’ll continue lobbying for it.