MQTT Number Entity Native Unit Comparison Error

[aneisch]

The problem

I have a number entity being created by an external device via MQTT Discovery:

command_topic: tesla_ble/climate-set-temp
state_topic: tesla_ble/number/driver_temp_setting
device:
  identifiers:
    - tesla_ble
  manufacturer: tesla-local-control
  model: Tesla_BLE
  sw_version: 0.4.1a-dev
  name: Tesla_BLE
icon: mdi:thermometer
device_class: temperature
unit_of_measurement: °C
qos: '1'
unique_id: tesla_ble_climate-set-temp
min: '15'
mode: slider
max: '28'
name: Climate Temp

The external device is publishing a temperature state:
tesla_ble/number/driver_temp_setting 24.5

My instance is set to use US Customary units vs. this device providing values in Metric. It appears that the number validation is currently done: raw value vs. native min/max instead of native value vs. native min/max leading to the error below. In this case I would expect 24.5 to be a valid state that HA would then convert to native units for frontend display.

2025-01-14 10:57:39.590 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.tesla_ble_climate_temp: 24.5 (range 59.0 - 82.4)

What version of Home Assistant Core has the issue?

2025.1.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

MQTT Number

Link to integration documentation on our website

https://www.home-assistant.io/integrations/number.mqtt/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

[jbouwh]

You are right. The comparison should be with native_min_value and native_max_value instead.

[jbouwh]

The linked PR should fix the issue.