To begin with this blueprint is still running solid for me (for now locally at least ) which is good because it will probably work for you as well. RWL021 is the same model I am using too.
It looks like there could be an update required for the blueprint if it is expecting a string instead of an int.
I will be happy to take a look and update the blueprint if needed though it may take some time.
If you’re handy with the YAML you could edit the blueprint directly, changing the field from an int literal to a str literal by putting quotations around each of the numbers on the subtype fields.
In the meantime another option you can try out are the new event entities. If you go down this route please do chime in here and we can share that info with others.
I am looking for a possibility to make double presses on a Hue dimmer switch work. Is this somehow possible, when you use a HueBridge (and not ZHA). At the moment I am using the iOS iConnectHue app to configure double/tripple/quadruple presses, but I want to bring the complete configuration/automation to Home Assistant.
I’m sure it’s possible to setup, packaging it up potentially through yaml or at least as a custom component. I’m unsure if we can natively detect the multiple presses, though I see the other blueprints using ZHA are able to get these events natively. Worst case scenario some custom logic would be needed to check how many presses are detected in a duration and trigger automations accordingly.
I’m happy to research existing solutions and check if there is a way to natively get the button presses since this is possible using ZHA. It might take some time though as I’m currently on vacation . In the meantime if you have any updates please feel free to share.
I was in contact with the developer of the native HueBridge implementation. He told me the following:
The native Hue api nor their matter bridge exposes that info. Also a Hue dimmer switch connected to ZHA/Z2M wont expose that info. You’re only option is to create a smart automation/blueprint to do this with counting the presses and checking the timeframe
I showed him the following Blueprint, where double presses are possible:
Got a chance to look through this blueprint and haven’t been able to replicate the message: “Message malformed: expected str for dictionary value @ data[‘subtype’]”. I’m using the latest Home Assistant version 2023.11.
At first, I thought subtype could be referring to properties within the blueprint itself, though I was able to validate the blueprint is working as-is. For good measure I re-imported the blueprint and created an automation, and all is working there with an RWL021.
I would recommend checking the automations you’re creating from the blueprint to validate they are setup as intended. Please let me know if there’s anything else I can do to help.
@codes Hi there, hope you’re doing well? Thanks for trying to find an answer to my error. But it appears that the error came mostly from me
Today I was able to make it work, by editing you’re blueprint on the blueprint menu of HA.
When I was doing it from the automations menu of HA, it doesn’t work.
Sorry to disturb you for nothing.
Hey @hoppel118, hopefully you’re doing well! I took a more thorough look at the existing blueprint shared and realized a couple things that have made me decide against extending the existing blueprint here.
For our current blueprint, we provide a single tap or long press action. This was extended by another user to have a repeat action when the button is held. These exist as two separate blueprints which are both shared here.
For the multi-tap actions that the other blueprint provides, there are additional requirements to track the state of the last press and logic to determine whether that press occurred within a duration to trigger a multi-tap action. Because of the additional helper required, users would need to setup this helper in order to use the blueprint.
Due to the extra helper requirement and logic required to test the different multi-tap gestures, I believe this functionality should be held in a separate blueprint. I’d also like to share that even at its current stage, we have a total of eight unique actions that can be selected with a single remote! I would encourage you or anyone else to use this blueprint as a foundation to implement multi-action functionality accordingly!
While I won’t be adding the additional functionality here, this blueprint still delivers on the key functions described above, and I believe it strikes a good balance of functionality to customizability. I’m jazzed that it’s worked so well for myself and that others are probably experiencing the same.
Appreciate your taking the time to post and happy automating!
Hey @codes thanks for your reply. Was a false alarm. I had an old entity in the blueprint which made the automation unavailable in the newer version of HA. Now that I have removed it, all is working again.
) which is good because it will probably work for you as well. RWL021 is the same model I am using too.
. In the meantime if you have any updates please feel free to share.
