-
-
Notifications
You must be signed in to change notification settings - Fork 108
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 Enhancements for Home Assistant #1162
Labels
Comments
Supporting templated topics like telegraf or similar tools do would work, allowing things like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I've recently attempted to integrate Diun into my Home Assistant installation for reporting docker image updates using the Home Assistant MQTT Update provider.
From the documentation:
The issue with the data provided from Diun is that it only contains information about the detected update. Ideally, the JSON payload could provide the "installed_version" and "latest_version" entries, as well as the container name and other attributes supported by this Home Assistant provider.
In addition, sending all updates through a single topic is not ideal, as this provider will only generate a single entity. A dynamic topic such as docker/diun/<container_name> would make things much easier.
Of course, a dedicate Home Assistant integration would be ideal from a user perspective, but this seems like the most direct way to integrate multiple container update entities with minimal configuration and state tracking.
The text was updated successfully, but these errors were encountered: