Inovelli Blue 2-1 switch losing triggers in HA when zigbee is rebooted

wardwolfram33 · April 24, 2024, 10:53pm

Hello Team,
Setting up the Blue switches is pretty easy - I ensure that I press the button combinations (such as “double up”) so that the trigger is an option in HA automations.

When Zigbee is rebooted in HA, these triggers are gone and unrecognized/undefined in HA automations. The only way I konw of to get them back, is to removed the Blue from HA’s Z2M, and re-add the device. This is not a great long term option and takes time.

Has anyone run across this? If so, what do you do to help eliminate this extra work?

Thanks in advance,

.

chack · April 24, 2024, 11:15pm

I don’t use Z2M personally so can’t speak too much to it, but I’d recommend either using rohan’s blueprint or manually specifying the triggers should work as shown here.

wardwolfram33 · April 24, 2024, 11:46pm

Thanks for the heads up chack, I played around with a few blueprint automatons,… .this might work. Thanks for your reply.

Twinkie · April 26, 2024, 5:27pm

I was having this issue for many of my devices using Z2M. I was running the official MQTT addon repository and after a little research, looks like MQTT was the culprit, at least for me. I came across this reddit post for others having issues with buttons. I switched to EMQX based on that discussion and I haven’t had an issue since. Wasn’t very difficult to switch over, took about 30 minutes. I wasn’t familiar with EMQX, but leveraged a Mostly Chris tutorial and it went smoothly. I also like the built in GUI that can help with problem solving and gives more control over the broker.

wardwolfram33 · April 26, 2024, 11:54pm

Thank you for sharing. I will definitely look at this.

msumma13 · May 9, 2024, 6:39pm

I’m having an issue with this as well. This is what my automation looks like now…

wardwolfram33 · May 9, 2024, 6:57pm

use this URL as your blueprint source. This blueprint has solved many of these issues…

github.com

rohankapoorcom/homeassistant-config/blob/master/blueprints/automation/rohankapoorcom/inovelli-vzm31-sn-blue-series-switch.yaml

# yamllint disable-line rule:line-length
---
blueprint:
  name: Inovelli Blue Series VZM31-SN Switch (Zigbee2MQTT)
  description: Create automations for the Inovelli Blue Series VZM31-SN Switch.
  domain: automation
  input:
    inovelli_switch:
      name: Inovelli Switch
      description: List of available Inovelli VZM31-SN switch.
      selector:
        device:
          integration: mqtt
          manufacturer: Inovelli
          multiple: true
    config_button:
      name: Config Press 1x
      description: Action to run, when the config button is pressed one time.
      default: []
      selector:

This file has been truncated. show original

msumma13 · May 9, 2024, 7:16pm

I just tried the blueprint and the config button didn’t do anything!

wardwolfram33 · May 9, 2024, 7:43pm

Hmmm. This blueprint allowed me to control lights, etc. when a automation trigger would not display the Inovelli Blue action in HA such as “single up” ,etc.

wardwolfram33 · May 12, 2024, 1:46pm

I am curious about this… such as, what is causing the Inovelli to lose these triggers? 1) Z2M 2) HA 3) Inovelli FW, 4) a combination of things?

Why I ask is that in the last 6-8 months, Zigbee has not gotten better for me. Besides working around this issue, I have to restart the Z2M bridge after HA core updates, etc. Thoughts?

bgreet · May 12, 2024, 2:39pm

That’s interesting, I’ve encountered the same problem whereas previously I did not have this issue (rebooting TubeZB to see devices). Also no longer picking up button presses on some of my devices. I may try out EMQX and see if its the mqtt broker