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

MQTT Events for Bifrost #74

Open
thk-socal opened this issue Jan 31, 2025 · 3 comments
Open

MQTT Events for Bifrost #74

thk-socal opened this issue Jan 31, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@thk-socal
Copy link

New Feature Request

I would love for bifrost to have it's own MQTT messages for the actions taken.

For example, a room/group of lights are controlled and color changes. Send an MQTT event for that so I can pickup the change and use that to drive further automations.

Some examples of automations:

  • Turn off adaptive lighting from other sources
  • Set RGBW LED strips (Non Hue / Non Zigbee / etc...) to a color profile match (I have RGBW controllers from Shelly that are joined via WiFi and controlled in Home Assistant. This would allow for me to match them to lights when bifrost makes a change.

MQTT Message: bifrost/group_name/event (JSON with the details)

@chrivers
Copy link
Owner

Isn't this already broadcast by zigbee2mqtt?

Perhaps surprisingly, even though Bifrost uses zigbee2mqtt, it doesn't actually talk mqtt at all :)

Instead, Bifrost connects directly to z2m, over the websocket port z2m uses for its frontend.

So implementing this would require Bifrost first gain mqtt support in general. That's doable, and I think worthwhile, but it's going to take some work.

@thk-socal
Copy link
Author

While the changes are in Z2M, how would I know it is a bifrost event, versus some other entity like Home Assistant changes? They key is knowing what is making the change to drive other things. Even if possible in a text field would work to know the change is from bifrost vs another thing.

@chrivers
Copy link
Owner

chrivers commented Feb 4, 2025

Ah, okay. That makes sense.

It's not supported right now, but we can keep this issue open as a feature request :)

@chrivers chrivers added the enhancement New feature or request label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants