Warning after reboot. TypeError: argument of type 'NoneType' is not iterable

Configuration Blueprints
,
48

There is an update available here (Version 2024.10.31). The last issue I had is now solved and everything is working as expected

As stated in a previous reply, a careful read of the mqtt trigger help solved the issue I was facing

      - conditions: '{{ "press_" | string in command }}'
        sequence:
          - wait_for_trigger:
              - trigger: mqtt
                topic: '{{ base_topic ~ "/" ~ controller ~ "/action" }}'
                payload: "release"
                value_template: '{{ value.split("_")[0] }}'

Enjoy and feel free to tell me if any errors are found

49

Thank you very much. But I need a few days, because I don’t have physical access to my PTM 215Z at the moment, too.

I’ll give you feedback.

50

Hey @chris-1243 , I tested your new version 2024-10-31. Unfortunately, it doesn’t work for me. Simple press commands to turn on don’t work. In the trace I could see that the hold command is being tried (brightness move for me).

I’m back to your version 2024-10-27. It still works.

51

Could use this link and try if the version 2024.11.04 is working ?

I found my mistake. Copy/paste human error…

52

Yep. This looks good and version 2024-11-04 works. Thank you very much! :+1:t2:

53

Great news!!! Thanks for your time

54

The thanks are due to you! After all, you are helping me too.

One more question, it’s not entirely clear to me. Would this blueprint also work with zigbee2mqtt 2.0? MQTT trigger can still be used and is not discontinued. Or is the affected action property still being used?

55

According to my reading and understanding, this blueprint should work with Z2M 2.0.

The recommanded way with Z2M 2.0 would be to use the event trigger as it seems easier than mqtt trigger.

Wait and see. It should have part of this new option in the next release.

56

Thanks for the clarification. That takes some of the pressure off.

It remains exciting. Let’s hope that the event trigger really does make things easier.

57

Hey, I tested latest-dev of Z2M based on the event trigger. For the PTM215Z/ZE, I do not see any benefits. The blueprint based on the MQTT trigger will work with Z2M 2.x.x without any issue.

There is an update available here. I cleaned a bit the code.

Feel free to test the blueprint based on the new event trigger here

58

Hi! Please excuse the late feedback, I was on vacation. I wish you all the best for 2025!

Thank you for the update.

I’ve already thought of that. Your version with the MQTT trigger works so well that you don’t have to replace it without need.

I will be happy to test the “event” version when I get the chance. But I will probably wait with z2m 2.0 until the first . Update, maybe until February. But still, thank you very much for your support!

Can you briefly explain to me why and what you have optimized?

59

It is only some syntax changes in some conditions. It reflects more what I have created for myself as well. It is also easier for me to maintain my own work.

Same functionalities.

60

Thank you for the explanation, I’ll take a closer look at it.

61

Hey @chris-1243 I’m now using your optimized version. As expected, it runs smoothly (with z2m 2.0 too). The optimization looks good as far as I understand it.

As soon as the event entities are no longer experimental at z2m, I will try that version in the future. But actually I find triggering on the native MQTT messages to be stable and perhaps more future-proof. They cannot become outdated so easily.

62

Have you ever considered sharing your awesome blueprints on Blueprints Exchange? I really like them.

Yes, I have created a topic and I do share some of my work (PTM216Z). Unfortunately, not the blueprint you are using. :wink: As it seems to work well, I will reconsider this statement and maybe I will share it.

63

Oops! I deleted that part from my post because I saw your post on Exchange later. Anyway, the fact remains: you did a great job.

64

No worries. Thanks… I will definitely share this one as well.

Time to definitely close this thread and move on a new one

65

Yes, you’re right. I marked your post with the update as the solution, as it eliminated the original cause of the error. All the best, I’m sure we’ll hear from each other again somewhere else sometime.

66

Let’s continue here.

I finally shared my work. Thanks to have been my beta tester :+1:

All the best, I’m sure we’ll hear from each other again somewhere else sometime.

All the best. Maybe on Github…

67

You’re welcome. After all, you helped me a lot.