Blueprint documentation tips/tricks and like "help"

Configuration Blueprints
1

Hello, I’ve been using homeassistant for some years now and I do make my own blueprints for my specific needs.

However, every now and then blueprints breaks due to updates and whenever at least I make new blueprint I either have to do a lot of trial and error or find a similar blueprint already publicly available because I just cannot find the appropriate documentations.

For example, I use Zigbee2mqtt (and I will move more and more towards mqtt based blueprints because they seem to make sense) but anyway, I had a script that worked flawlessly with conbee2 + Zigbee2mqtt + the standard MQTT integration with mosquito.

The trigger to that particular blueprint were a state change based on the “action” which is available in the payload.

Then, I changed to slzb-06 + Zigbee2mqtt + the standard MQTT integration with mosquito and that blueprint stopped working.

I had to remake the blueprint to use mqtt specifically but that’s my issue, why did the previous blueprint work with the previous antenna and why did it stop working now, where’s the docs that tells me what works with what?
For example conbee 2 might have a different payload that slzb-06 I dunno but if it does, where’s the docs?

And we’re do I find the docs about what device domains there are, what actions is available for state changes, events etc etc.

There’s so much I feel is missing I just get frustrated when dealing with it, enough so that I’ve been close to changing to honey pro multiple times but once again I’m stubborn and there gotta be good documentation out there?

2

Hi snowless0031,

Blueprints are written by individuals such as myself, and it is the responsibility of the Blueprint Author to document what they did for the user. Not all Blueprint Authors understand or do this, unfortunately. I personally attempt to over document my Blueprints as an attempt yo reduce my support load, and for the most part it works. For instance I just did a YT video on how to write a Blueprint.

All pieces of hardware are different with different controls and not all of them are documented.

So it may be frustrating, but this is the current landscape. Trial and error is a big part of writing the automations that Blueprints are based on. You may be doing blueprints, but you are asking questions about automations or scripts really.

Feel free to look at the documentation on my Blueprints and copy anything that helps you.

My Blueprints