-
Notifications
You must be signed in to change notification settings - Fork 400
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
🚀 | Add MQTT component to support control via Smart Home solution #1963
Comments
MQTT is not yet implemented https://rpi-jukebox-rfid.readthedocs.io/en/latest/featurelist.html#feature-status But pull requests and contributors are always welcome! @pabera @ChisSoc |
Wonderful feature which could use a pull request :-) |
For anyone interested in implementing this feature, here are some thoughts how this could be done: |
More then a year later. I started working on this topic. Finally. Basic mqtt updates are working already now need to see which other values I need to map and how I implement the mqtt commands. Once this is done I will add some test and open up the PR. But this is the first time I work with zeromq. Not sure if I followed the architecture and the ideas you linked to @s-martin . So any initial thoughts or quick feedback would be appreciated. Here is the WIP implementation https://github.com/c0un7-z3r0/RPi-Jukebox-RFID/blob/future3/add-mqtt/src/jukebox/components/mqtt/__init__.py |
Thanks for starting the work on this feature! 🎉 We will look into it. |
Feature Description
Add MQTT component to Future3.
What functionality would you like to see in your phoniebox v3.x?
Integration with Smart Home solutions like Home Assistant via MQTT. Similar to how it is implemented in version 2.x
How do you envision the feature to work from a users perspective?
As the user I can configure the connection to my MQTT broker via the jukebox.yml. Then the phoniebox is connecting to the broker and starts broadcasting various status messages e.g. Playerstate, Volume ....
But It can also then be controlled via MQTT to allow for example via Home Assistant to mute the player.
The status of the connection to the broker should be easily visible in the webapp.
Further information that might help
The features should be on par with to how version 2.x has implemented plus potentially additional features that might be useful.
I am happy to build this functionality since I already contributed to the version 2.x mqtt solution previously and would like to migrate my two phonieboxes to version 3.x (no MQTT support is blocking this currently).
The text was updated successfully, but these errors were encountered: