Aqara Double Rocker Switch

Going mad with Zigbee and adding a few more devices.

I am wondering how I should define this Aqara Double Rocker Switch as a Shim device. It is a momentary push device and you can get six states called "click" from it as follows:

Code: Select all

zigbee2mqtt:info  2020-02-21 17:57:53: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":120,"click":"left"}'
zigbee2mqtt:info  2020-02-21 17:57:57: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":123,"click":"left_double"}'
zigbee2mqtt:info  2020-02-21 17:57:59: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":123,"click":"left_long"}'
zigbee2mqtt:info  2020-02-21 17:58:01: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":113,"click":"right"}'
zigbee2mqtt:info  2020-02-21 17:58:02: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":110,"click":"right_double"}'
zigbee2mqtt:info  2020-02-21 17:58:04: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3055,"linkquality":107,"click":"right_long"}'


It doesn't have an ON/OFF state as such.

For that one, I would set it up as a value sensor, with the battery or linkquality as the primary value. And set up the multi-states key as ".". Then just set up a trigger on the "click" device state and do whatever you want from there.

You could set up six triggers like that, each with a different condition to test the value of that device state.

Thanks for the pointer - I'll give a try.

Good work Jon. I've got one on order but not arrived yet.

I've got one of these on order too

https://www.zigbee2mqtt.io/devices/WXCJKG13LM.html

For that one, I would set it up as a value sensor, with the battery or linkquality as the primary value. And set up the multi-states key as ".". Then just set up a trigger on the "click" device state and do whatever you want from there.

You could set up six triggers like that, each with a different condition to test the value of that device state.

As expected, I can confirm this works OK.

Nice.

I have now set this up as a MQTT Generic JSON device. I have also setup triggers for it e.g.:

• Type: Device State Change
• Device:
  
  • Aqara Double Rocker 1
  • click
  • becomes Equal to: right

This works fine except for one issue which is that when I press the same button again (e.g. right in this case), no trigger is actioned as the field content hasn't changed.

So I looked at a Z-Wave Switch and I see that that is triggered on the incoming Z-Wave Command received from the device - button 1 pressed for example. It doesn't matter if that was the button previously pressed, it will invoke the associated action again.

The command from the the Aquara Double Rocker Switch is e.g. :

Code: Select all

zigbee2mqtt:info  2020-02-23 11:48:07: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3115,"linkquality":84,"click":"right"}'

I couldn't instantly work out whether it is possible to trigger on the topic zigbee2mqtt/Aqara_double_rocker_1 plus payload "click":"right"?

Another way which could work is for the state to be cleared maybe by the MQTT SHIMS plugin providing an action that can allow a state to be set to specific value e.g. blank in this case. I could then set the trigger to have a condition that it only fired if the state was non-blank and and an action to clear the state.

See my comments on the button. I have a delayed action when click equals single to send a mqtt message with click ='' ie null. Next press is then recognised.

I have to do the same on my flic buttons.

See my comments on the button. I have a delayed action when click equals single to send a mqtt message with click ='' ie null. Next press is then recognised.

I have to do the same on my flic buttons.

Thanks for the tip - I'll give that a try

Hmm. I hadn't really been considering buttons or keypads when I designed the Shims plugin.

I could either add a timestamp state which will always be different when a new message for that device is received. Or a specific Event to trigger so you don't need to trigger on the device state changing. In either case, since you're not triggering on the "click" state, you would need to check that in the conditions of the trigger. I think I'd prefer the Event, since then there's no chance of a state name collision.

Either would be helpful as it means that it is maintained in one trigger and you don't need to worry about resetting the state.

Coincidentally, I just noted these two entries in the log. The first was unsolicited and the second because I pressed a button:

Code: Select all

zigbee2mqtt:info  2020-02-23 13:55:54: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3105,"linkquality":110}'
zigbee2mqtt:info  2020-02-23 13:56:39: MQTT publish: topic 'zigbee2mqtt/Aqara_double_rocker_1', payload '{"battery":100,"voltage":3105,"linkquality":107,"click":"right"}'


Note that the first unsolicited message doesn't include the click state. Thought I should advise this as not sure what impact it might have on your proposed solution.

Pre-release 0.2.4 - https://github.com/FlyingDiver/Indigo-S ... /tag/0.2.4

Added trigger event for device update.

That works

However, when I first went to set up the condition, the click state wasn't listed. I assume because there had been an interim unsolicited update and that state wasn't included and so MQTT Shims removed the state. As soon as I clicked the button and re-edited the trigger condition, the click state was present. I am not sure what will happen if a message comes through and the state is removed?