Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Committed 20250130-yarafie-massive-update #677

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

yarafie
Copy link
Contributor

@yarafie yarafie commented Jan 31, 2025

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.

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
These Blueprint have 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.

Copy link
Contributor

github-actions bot commented Jan 31, 2025

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!

@yarafie
Copy link
Contributor Author

yarafie commented Jan 31, 2025

@EPMatt hope your exams are going well.

Since I had some time on my hands, I went through everything.
The more I looked the more impressuve this whole setup is.

Anyways, I managed to do several things with this PR and it completly removes the need for my previous PR so I will delete it.

Summary of changes:

  1. Updated .github/workflows to latest npm 22

  2. Updated website build runs (docusauraus etc.)
    With the 2 above most dependabot PR's not needed

  3. Updated as before blueprints/hooks and their docs to remove entity

  4. Added new controller IKEA RODRET (Done a little differently) check it out as with this blueprint no need to select which Integration is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant