iād have sworn up and down i was using the deconz one
i suppose thatās what happens when you try this stuff before bed haha
for my own sanity, this:
regex_match("^{(("a":.*|"t":\d+.\d+)(,)?){2}}$"))
is the correct string, isnāt it?
Iāve replaced the regex that appears on lines 439 and 440 of the blueprint, but itās still not working for me - Iāll be honest, I suck at regex, and Iām not even sure where I should start to begin troubleshooting. If someone could point me in the correct direction, Iād be eternally grateful.
i donāt suppose anyone has any ideas as to the above?
iāve tried mucking round a bit over the last couple weeks, and i just canāt seem to get it working as it should with the double presses
the single press works fine, but no matter what i do, the double press just doesnāt seem to work
near as i can tell itās gotta be something else - the traces on the automation seem to be fine, the controller is firing 5002 and 4002 events on the right and left buttons, and the time looks to be correct as well - the automation just isnāt picking up the double presses, and iām legitimately bamboozled as to why
the regex for deconz above in the thread wasnāt parsing the quotes around the āaā properly, and needed to be escaped for a literal match, as with the ātā
I learnt quite a bit about regex tonight! thanks for the help @Nick4
it was absolutely something else, and iām glad i wasnāt going nuts
Iāve installed this and added the latest regex modā¦ but I canāt seem to get the up, left, right, or down buttons to work. Only the center button (but both for click and double click.)
Trace shows:
Triggered by the event 'zha_event' at September 21, 2023 at 9:29:36 PM
Test Test if 2 conditions matches
Delay for 50 milliseconds
Define variables trigger_action, trigger_delta, and last_controller_event
Call a service 'Input text: Set' on
(input_text.julieremotelastcontrolledevent) turned {"a":"step_with_on_off_StepMode.Up_43_5","t":1695346176.657274}
Choose: No action taken
Finished at September 21, 2023 at 9:29:36 PM (runtime: 0.06 seconds)
I am having some trouble with the automation and light groups.
Whenever I turn my light group on/off using this automation, things work as expected.
However, if I turn the light group on directly, using HAās native light card, one of my lights are always at lowest brightness, every time. I didnt have this issue when I used other blueprints for the 5-button remote.
Any idea how I could solve this?
Hi - Love this blueprint. Iām using ZHA and my up/down E1810 buttons werenāt working. I noticed the ZHA event string didnāt match the blueprint. I updated it to the following and itās working now:
I got my IKEA E1810 with a Tradfri RGB-light setup in my HA. Everything is working great. However, when I change the color (for example, warm white to RGB) I cannot get the warm white back. Only the RGB colors such as blue, red, green, yellow, orange etc.
Now, Iāve tried setting up a āCenter button long pressā in order to restore the color temperature to 370 mireds. But this is not working. Am I doing something wrong? Z2M integration.
Call Service (Light Toggle, Color Temp 370 Mireds)
@LewisSpring I overrided the current blueprint with yours. For the Center button long press iāve set Color Temperature to 370 Mireds (as mentioned). However, when I press the center button the light immediately turns off.
Long press center button does not change the light color with the call service light.toggle on 370 Mireds color temperature.
Hi everyone, when I use this (very awesome!) Blueprint, the z2m log throws three entries on a single click (doesnāt matter which button). It looks like this:
MQTT publish: topic 'zigbee2mqtt/Remote Family Room Lights', payload '{"action":"toggle","battery":90,"linkquality":102,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"},"update_available":false}'
MQTT publish: topic 'zigbee2mqtt/Remote Family Room Lights', payload '{"action":"","battery":90,"linkquality":102,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"},"update_available":false}'
MQTT publish: topic 'zigbee2mqtt/Remote Family Room Lights/action', payload 'toggle'
Is this the expected behavior? As far as I can tell, the automation does what itās supposed to, but I am confused by this. Timestamps are identical to the second.
I believe this is normal as the payload/action is changing. The action/state will change momentarily in Z2M and go back to being blank afterwards. This is why a Input Helper is needed in Home Assistant to keep track of the last action, I believe.
I recommend that new and existing users move to the Redux version of the blueprint.
For future support on the Redux version of this blueprint and instructions on how to download it, please post there.