Usermod BME280: Fix "Unit of Measurement" for temperature#4360
Merged
Conversation
The Unit of Measurement ("tempScale") of the MQTT message is set for each published measurement - but not for the homeassistant discovery.
Thus, openhab (and mabye other systems?) don't recognize the value as "Number" - so it uses String instead. This is somehow annoying when trying to configure the sensor channel to be linked to an existing item in OpenHAB.
(Items that are created automatically or with "Add point to model" can be configured in a way that the String is transformed to Number or Number:Temperature, but existing Items cannot be linked).
When a "Unit of Measurement" is set in HomeAssistant discovery, the HA binding of OpenHAB notices that the MQTT String is a number and automatically converts it.
Author
|
MQTT Message on Before Change: {
"name": "WLED Ian Tray Temperature",
"state_topic": "wled/ian-tray/temperature",
"unique_id": "WLED-Ian-TrayTemperature",
"device_class": "temperature",
"expire_after": 1800,
"device": {
"name": "WLED Ian Tray",
"identifiers": "wled-sensor-WLED-Ian-Tray",
"manufacturer": "WLED",
"model": "FOSS",
"sw_version": "0.15.0-rc1"
}
}After Change: {
"name": "WLED Ian Tray Temperature",
"state_topic": "wled/ian-tray/temperature",
"unique_id": "WLED-Ian-TrayTemperature",
"unit_of_measurement": "°C",
"device_class": "temperature",
"expire_after": 1800,
"device": {
"name": "WLED Ian Tray",
"identifiers": "wled-sensor-WLED-Ian-Tray",
"manufacturer": "WLED",
"model": "FOSS",
"sw_version": "0.15.0-rc1"
}
} |
euphi
changed the title
Collaborator
|
I neither use MQTT nor the BME280 mod, but seems like a valueable addition to me. |
Pluto1010
pushed a commit
to Pluto1010/WLED
that referenced
this pull request
Sep 1, 2025
Usermod BME280: Fix "Unit of Measurement" for temperature
softhack007
pushed a commit
to MoonModules/WLED-MM
that referenced
this pull request
Jan 17, 2026
Usermod BME280: Fix "Unit of Measurement" for temperature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The Unit of Measurement ("tempScale") of the MQTT message is set for each published measurement - but not for the homeassistant discovery.
Thus, openhab (and mabye other systems?) don't recognize the value as "Number" - so it uses String instead. This is somehow annoying when trying to configure the sensor channel to be linked to an existing item in OpenHAB. (Items that are created automatically or with "Add point to model" can be configured in a way that the String is transformed to Number or Number:Temperature, but existing Items cannot be linked).
When a "Unit of Measurement" is set in HomeAssistant discovery, the HA binding of OpenHAB notices that the MQTT String is a number and automatically converts it.
See also openhab/openhab-addons#6663 .