sorry for my late response. I eventually found what was causing your issue: in detecting the double press action, a comparison between 2002 from the action_mapping variable, and '2002' from the text helper was made. The condition would always produce a falsy value when using deCONZ, since comparing a number and a string returns false.
Iāve just updated the blueprint with the fix. Please let me know if the automation now works as expected.
Moreover, Iād like to point out that the problem was present on the majority of controller blueprints. Your feedback helped to improve all of them as well, so thank you very much for reporting.
sorry for my late response. Iāve opened a Pull Request which will hopefully solve this issue. Iām now waiting for confirmation that the problem is solved for the user who opened the linked issue on GitHub.
In the meantime, you can test PR changes by importing the following blueprint into your Home Assistant instance.
Iām using a couple of your automations, your work is excellent, thank you for sharing all these automations/blueprints.
Iād love to use this specific one, but for the switches I use in my house, I have 10 OSRAM Smart+ Switch Mini, I guess it wouldnāt work.
Iāve found another blueprint that supports that switch, but itās specific for Zigbee2MQTT.
Since you are trying to support all platforms for each switch, I was wondering if you could make a version of your blueprint for that switch, or if you can help me understand what I need to modify to adapt it to that device.
Thank you again for your contributions, I really appreciate it.
Hi @alexdelprete, thank you for your feedback! Really appreciate it.
Iād love to use this specific one, but for the switches I use in my house, I have 10 OSRAM Smart+ Switch Mini, I guess it wouldnāt work.
Yeah, we need to develop a Controller blueprint specifically for the OSRAM Smart+ Switch Mini. Iāve just opened an issue on the Awesome HA Blueprints GitHub repository to track the progress of your feature request:
Iāll try to look around for ZHA and deCONZ action mappings for this remote, so we can implement support for those integrations as well. Iāll let you know as soon as the blueprint is ready for testing.
By the way, which integration are you using to connect the OSRAM Switch to Home Assistant?
You might also want to look at the integration I linked in previous post, thereās a trigger section that the dev says is necessary because of the way the switch behaves.
If you need me to test/debug something for you, please let me know, I use ZHA with a Connbee II. If I can help finding the action mappings please instruct me on how to do it and Iād be glad to help you.
For now Iāve done everything manually with standard automation, I have 1 automation for each button for each switch. The list of automations is exploding since I have many switches. Thatās why I need something like your integration.
You might also want to look at the integration I linked in previous post, thereās a trigger section that the dev says is necessary because of the way the switch behaves.
Thank you for pointing it out, Iāll include that required check in the blueprint.
If you need me to test/debug something for you, please let me know, I use ZHA with a Connbee II. If I can help finding the action mappings please instruct me on how to do it and Iād be glad to help you.
As reported in the linked GitHub issue, I was able to identify the mappings for both ZHA and deCONZ, but thank you for being available anyway.
Itād be extremely helpful if you could test the blueprint before making if publicly available. Iāll let you know on GitHub as soon as the PR with the new blueprint is ready for testing.
For now Iāve done everything manually with standard automation, I have 1 automation for each button for each switch. The list of automations is exploding since I have many switches. Thatās why I need something like your integration.
Great to know, so a blueprint will definitely be useful in your use case.
Absolutely, canāt wait to help you in any possible way. Let me know.
It will be fantastic, right now my automations list requires me to scroll down some pages, one automation for each button of each switch/controller. You can imagine the chaos, and I donāt like chaos. Thatās why I asked if you could support the controller Iām using.
Great, weāll get in touch for testing the new blueprint. I also saw your other FR on GitHub, Iāll look into that after weāre done with the OSRAM remote.
It will be fantastic, right now my automations list requires me to scroll down some pages, one automation for each button of each switch/controller. You can imagine the chaos, and I donāt like chaos. Thatās why I asked if you could support the controller Iām using.
I can imagine how many automations youāre currently runningā¦but luckily Controller blueprints are here to help.
2021-05-23 01:29:21 ERROR (MainThread) [homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer] Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 5: Choose at step 1: choice 1: Error executing script. Invalid data for call_service at pos 1: not a valid value for dictionary value @ data['entity_id']
2021-05-23 01:29:21 ERROR (MainThread) [homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer] Controller - IKEA E1743 On/Off Switch & Dimmer: Choose at step 2: choice 5: Error executing script. Invalid data for choose at pos 1: not a valid value for dictionary value @ data['entity_id']
2021-05-23 01:29:21 ERROR (MainThread) [homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer] Controller - IKEA E1743 On/Off Switch & Dimmer: Error executing script. Invalid data for choose at pos 2: not a valid value for dictionary value @ data['entity_id']
2021-05-23 01:29:21 ERROR (MainThread) [homeassistant.components.automation.controller_ikea_e1743_on_off_switch_dimmer] Error while executing automation automation.controller_ikea_e1743_on_off_switch_dimmer: not a valid value for dictionary value @ data['entity_id']
and on short press i get these warning but is working:
2021-05-23 01:29:28 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'click' when rendering '{{ value_json.click }}'
2021-05-23 01:29:28 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'action' when rendering '{{ value_json.action }}'
Since your device in connected to HA via Zigbee2MQTT, you need to provide a valid input_text entity for the helper_last_controller_event input.
Moreover, Iād suggest you to update the blueprint to the latest version Iāve just published. Please read the changelog in the original post to learn more about whatās changed. With the latest update, the helper_last_controller_event input is strictly required.
To learn more about the helper_last_controller_event, how itās used an why itās required, you can read this section in the official documentation.
The warnings you see in the logs are not relative to this blueprint, but on how Zigbee2MQTT exposes the device itself to Home Assistant. Which version of Zigbee2MQTT are you running?
Okey iāve added the helper_last_controller_event input_text and it started working, pretty laggish (ie i keep pressing O to dim a bit than release and short press it will not turn off the light, wait ~10sec and it will start back working) no more errors in the logs but warnings still here on each button press.
probably itās due to the Zigbee2mqtt integration or idk but the long press action to dim is just unreliable
Zigbee2MQTT is keeped updated (or at least it should autoupdate) so actually is 1.18.1-1, but i see that 1.18.3 is outā¦
EDIT:
okay upgraded to 1.18.3-1 (they changed github repo URL and never noticedā¦), still having this warning on each button press, and long press, working a bit but still causing unreliability
2021-05-27 17:44:04 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'click' when rendering '{{ value_json.click }}'
2021-05-27 17:44:05 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'click' when rendering '{{ value_json.click }}'
The warnings youāre reporting are probably relative to Zigbee2MQTT still not reporting entity states as expected by Home Assistant, since we are not using any click variable in the blueprint templates.
Regarding the stability issues, I suggest you to test the blueprint with custom actions such as the following:
This action doesnāt rely on any external integration which might cause stability issues (e.g. if your lights are connected via Zigbee2MQTT too, the messages sent by the remote can slow down the network, especially if youāre using a slow Zigbee Coordinator such as the CC2531).
Let me know if you have any news regarding this issue.
Thanks!
Thank you for your feedback. Iām glad to hear that your issue is solved.
probably you should consider not working some behaviours with Z2M
Multiple users reported the controller blueprint fully working with Zigbee2MQTT; the issue might be with your Zigbee coordinator not being completely supported by Zigbee2MQTT (such as the Conbee II, whose support is currently experimental) or with the USB stick being too little for your Zigbee network (such as the TI CC2531 with 20+ devices paired, which can cause multiple stability issues).
Trying to set this up with an ikea 5 button remote and the light hook. I have confirmed the remote is sending messages and tried it with another blueprint, it worked as expected. I am trying to use the light hook.
I get no actions being executed.
I see this error but as I am using zha I have left the entity empty and used the device.
Stopped because an error was encountered at June 3, 2021, 2:42:32 PM (runtime: 0.03 seconds)
not a valid value for dictionary value @ data['entity_id']``
