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

Bug - Z2M 2.0 will break all blueprints in January 2025 #622

Open
1 task
dagstuan opened this issue Dec 1, 2024 · 0 comments
Open
1 task

Bug - Z2M 2.0 will break all blueprints in January 2025 #622

dagstuan opened this issue Dec 1, 2024 · 0 comments
Labels
blueprint An issue related to a blueprint bug Something isn't working

Comments

@dagstuan
Copy link

dagstuan commented Dec 1, 2024

Blueprint name

All blueprints

Home Assistant Core Version

Home Assistant Installation Type

Home Assistant Core

Description

As mentioned in the latest release notes: Zigbee2MQTT 2.0 is planned to be released in January 2025. It will remove the homeassistant_legacy_triggers currently required to trigger these blueprints. Hopefully they can be updated in time.

Zigbee2MQTT docs suggest moving to MQTT device triggers instead of the sensor.*-triggers. Docs for breaking changes are here.

I saw #244 but I figured it would be nice with a new issue for visibility, since that one is quite old.

Automation YAML config

-

To Reproduce

Upgrade to Z2M 2.0

Expected behavior

Blueprints supporting MQTT device triggers.

Actual Behaviour

Currently no support for MQTT device triggers.

Additional Details

  • I'd like to help developing a fix for this issue.

Screenshots

No response

Additional context

No response

@dagstuan dagstuan added blueprint An issue related to a blueprint bug Something isn't working labels Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blueprint An issue related to a blueprint bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant