Ikea E1743 only respond to short press about awesome-ha-blueprints HOT 8 CLOSED

Hi @EPMatt !
That sounds great!
I'll definitely do that later today.
Thanks again for the effort making these blueprints (Y)

from awesome-ha-blueprints.

Hi @bkje14, thank you for taking the time to report here.

I had an automation configured with short, long and double clicks that have been running smoothly for weeks since i set it up.

Have you recently performed some relevant changes to your system, which might have interfered with the automation (eg. updated Zigbee2MQTT, updated the blueprint etc.)?

Moreover, just to make sure, are you running the latest version of the blueprint?
You can update the blueprint by deleting it from the Configuration->Blueprints panel, then importing it again with My Home Assistant / Direct Link from the blueprint documentation.

Thanks!

from awesome-ha-blueprints.

Hi @EPMatt
First, a big thanks for the awsome blueprints you make! they are truly wonderful.

At first i suspected the z2m integration to be the culprit, at I did indeed have it on auto update so i recieved the newest a couple of days ago, and that could of course be the reason. However, when hooking the remote up to simpler automations there seems to be no errors occuring, which led me here.

I just reinstalled the latest version of the blueprint at tried that. The same thing happens, no actions are performed when the double click or long press actions are configured.

Here is a z2m log of doing a short_up_press action.
It is a little hard for me to see if this is as expected or not.

After having read a little about it I can understand that is expected that multiple events are occuring even when only doing one press. I am though a little suprised by the third having a "action": null

I saved the 5 automation traces that came out of that click.
automation_trace.zip

three of them seem to be handled as expected - being supressed as not real clicks.
Two of them results in an error:
first of the five traces:

last of the five traces:

lastly, i checked the ìnput_textfor the double clicks via the developer console. even when the automation fails it actions the correct button click is saved in the helper. for long presses it stores thebrightness_move_up` and for double clicks it saves "on" for the first and clears it for the second click.

Let me know if there is any thing I can test or check on my end, i'll be happy to help.
I will also try and dig in and see if i have a snapshot with an older version of z2m.

Best regards,
Bjørn

from awesome-ha-blueprints.

Well, you where right in your initial assumption.
I found a snapshot with the previous z2m version 1.18.2-1 and that solved the issue.
Automations work as expected again.

Looking at the z2m logs, the only difference i see is this action:null
But i will try and ask over at the z2m repo what might be the culprit of this.

Thank you very much for the help and time you put into this.
If you ever need someone to test new things, i would be happy to help out.

from awesome-ha-blueprints.

Hi @bkje14, thank you for reporting and for your nice feedback.

I'm happy to hear that your issue is solved by downgrading z2m. :)
I guess the problem is that the blueprint picks the event up, and it does not filter it since action!="". The issue might be with zigbee-herdsman-converters, which is the component responsible for providing device support, and not with Zigbee2MQTT itself.

Thank you very much for the help and time you put into this.
If you ever need someone to test new things, i would be happy to help out.

Thank you, I'm glad to hear that this blueprint is useful for you. I'm planning to increase the number of supported controllers, so if you have any device which you'd like to be included in the Controllers blueprint collection please let me know.

Moreover, if you notice some PR/issue which you'd like to contribute to you can always jump into the discussion and post your opinion there. Any kind of contribution or feedback is highly appreciated. :)

Thanks again!

from awesome-ha-blueprints.

Hi @bkje14,

I'm closing this issue since your original problem is solved. If you need any additional guidance don't hesitate to open a new issue or create a discussion, I'll be glad to help. :)

Thank you and happy automating!

from awesome-ha-blueprints.

Hi @bkje14,

I've some news regarding this problem. I raised an issue on the zigbee-herdsman-converters repo regarding the E1743 controller (Koenkk/zigbee-herdsman-converters#2618).
It looks like the device reporting null states is actually a feature part of a recent z2m update, which was implemented due to how Home Assistant now requires template rendering in entity states.

I've updated all the controller blueprints to support this change, with backward compatibility. You can now safely update Zigbee2MQTT to version 1.18.3. Just make sure to delete the blueprint and import it again to get the latest changes. :)

from awesome-ha-blueprints.

Hi there,

🔒 This issue has been automatically locked since there has not been any recent activity after it was closed.
Please open a new ticket for related bugs.

Thanks!

from awesome-ha-blueprints.