Always update sensor_name after resolving hostname #144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My pi's weren't registering correctly and I was getting a lot of MQTT traffic with rpi_{hostname}.
This is because the "default_sensor_name" is not the same as the MQTT.sensor_name config, and yet the default sensor name is being used to validate whether to set the hostname.
Until the logic for reconciling the MQTT config and the default sensor name is more meaningful, it's better to just ALWAYS set the sensor name correctly.