Mass Migrate to zigbee2mqtt MQTT device triggers (mqtt)

[yarafie]

Thank you for taking the time to work on a Pull Request. Your contribution is really appreciated! 🎉
Please don't delete any part of the template, since keeping the provided structure will help maintainers to review your work more rapidly.

Sections marked as * are required and need to be filled in.

Migrate to Zigbee2MQTT MQTT Device Triggers.

Breaking change

⚠️ Breaking Change:

Migrate to Zigbee2MQTT MQTT Device Triggers. (@yarafie)

The controller_entity input has been deprecated, and controller_device is now mandatory.

If you are a Zigbee2MQTT user and plan to update this blueprint, please make sure to remove the controller_entity input from your automation config and add the device ID of your controller to the controller_device input.

To obtain the device ID from your controller, configure the automation from the UI and use the device selector dropdown on the controller_device input to select your controller.

Additionally you need to be using no less than Home Assistant Version 2024.10.0

Proposed change*

With zigbee2mqtt version 2.x, legacy features are planned to be removed and are disabled by default if you have updated to zigbee2mqtt version 2.x.

Further information can be found in in the zigbee2mqtt discussion link below:

Zigbee2MQTT 2.0.0 breaking changes

Koenkk/zigbee2mqtt#24198

This Blueprint has been updated to make use of MQTT device triggers and deprecate the legacy entity action sensors (sensor.*_action). If you have legacy or even the experimental entities enabled in zigbee2mqtt (i.e. set to true) in your zigbee2mqtt configuration the blueprint should still work as it does not use them.

Checklist*

• [Y] I followed sections of the Contribution Guidelines relevant to changes I'm proposing.
• [Y] I properly tested proposed changes on my system and confirm that they are working as expected.
• [Y] I formatted files with Prettier using the command npm run format before submitting my Pull Request.

[github-actions]

Hey @yarafie, thank you so much for your contribution! 🚀

🔄 We're currently running a few checks to make sure that everything is great with your contribution.
If further actions need to be performed before your contribution can be reviewed, additional guidance will be provided to you in the next comment.

Results are coming soon, stay tuned!

[esolitos]

cc: @EPMatt for visibility. :)

[EPMatt]

Thanks @yarafie for the contribution and @esolitos for the ping. :)
Currently under exams at university so I'm unable to review this PR for the next few days.

ETA looking on this is approx one week (04/02-05/02).
Thank you all for your patience!

[esolitos]

No worries, thanks for your time. I only pinged you because you might not get notifications from PRs. 😄

Best of luck with your exams and once more thanks for the time dedicated to this project!

[smarticu5]

For anyone also watching this PR (and I'll echo what @esolitos said, best of luck and thank you for everything you do to support this, EPMatt), I've been able to just import the blueprints which are being merged by this PR. I'll move back over to this main repo once merged, but my automations are back to working in the meantime.