-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Update to latest valetudo-mapper #442
Conversation
Rsync-local updates
Update to latest valetudo-mapper which contains some fixes for the new Home Assistant MQTT format
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will dynamically always use the master branch instead of a fixed version.
This need to be changed to the latest commit hash, if no tag can be used.
Changed it to the latest commit. Do you expect any issues when using the latest version on master? |
When using master, the container content is not fixed. So the same build can produce different outputs on two different dates. |
@Poeschl can you have a look at this PR? The current format gets deprecated in the next Home Assistant release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reminder, the changes looks good now.
I will make some time this week to go over the PRs.
Update to latest valetudo-mapper which contains some fixes for the new Home Assistant MQTT format.
It should fix the following warning which gets deprecated in 2024.2 release.
MQTT entity name starts with the device name in your config {'name': 'rockrobo_map', 'unique_id': 'rockrobo_map', 'device': {'manufacturer': 'Roborock', 'name': 'rockrobo', 'identifiers': ['rockrobo'], 'connections': []}, 'topic': 'valetudo/rockrobo/map', 'availability_mode': 'latest', 'payload_not_available': 'offline', 'encoding': 'utf-8', 'qos': 0, 'enabled_by_default': True, 'payload_available': 'online'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_map'