For me the 100k sensors swings ±3C approx.
The 10k that was in the box swings about ±0.5C but I cannot get that into the floor so… ;(
I have created a support ticket to Aqara, this is clearly an issue that several are experiences. Found someone on reddit with the same problem.
Thanks everyone for sharing your experience. Is the W500 a good mesh router? What’s your experience here?
I’m not sure how to measure ‘good’, but they seem to act as routers okay, according to the visulization tool. “Bathroom floor” and “Livingroom floor” are both W500s in the screenshot, and seem to be routing other zigbee devices well enough.
Oh that is great to know. Thank you! I am still using a TS0601 by _TZE284_rlytpmij and they show up as routers but don’t route anything. They look better though 
If W500 are fully ZHA compatible I might consider swapping them out.
Hi guys, I am quite new in Home Assistant Community and I have recently purchased Aqara W500 thermostat.
Quick info for people who have issue with the floor sensor reading (NTC): this thermostat uses a mapping table of beta = 3950 and supports 10, 50 and 100k Ohm. Previously I was using (most probably) beta = 3435 with 100k Ohm and I was having a temperature varying between ~15.5 and ~20.5 degrees Celsius. After replacing sensor with the one that comes with the device, temperature varies between 19.4 and 19.9 degrees Celsius (±0.3 degree Celsius), which makes sense as resistance changes.
Okay, now going to the part that I am most interested with 
It has a selection sensor to external, however I don’t see a sensor like external_sensor_temperature or any other way of publishing the external data. Have you got any ideas how it can be done? I would like to order 2 more thermostats and would like to know if this kind of automation is possible
Hi guys, I was able to find a workaround for external sensor, feel free to use the YAML automation as below: in short, I am comparing an internal sensor reading with a external sensor that I want to use and I am adjusting a temperature difference to match the external sensor value. Once external sensor temperature updates, it will update the temperature difference as well
alias: Thermostat bathroom temperature
description: ""
triggers:
- trigger: state
entity_id:
- sensor.temperature_bathroom_temperature
conditions: []
actions:
- action: mqtt.publish
metadata: {}
data:
topic: zigbee2mqtt/Thermostat bathroom/set/local_temperature_calibration
payload: |-
{{ (
states('number.thermostat_bathroom_local_temperature_calibration') | float(0)
+
states('sensor.temperature_bathroom_temperature') | float(0)
-
state_attr('climate.thermostat_bathroom', 'current_temperature') | float(0)
) | round(1) }}
For reference:
Edit Updated the code
Good solution! However, the main limitation is that the calibration range is only ±2.5°C.
I’m using an external floor sensor to measure the actual floor surface temperature, and the difference between floor and air can easily reach ±10°C. My goal is to have warm floors, not just heated air 
The only solution I found is using the Advanced Heating Control blueprint with generic calibration.
Pros:
Cons:
If the ±2.5°C range works for your setup, I’d still recommend this blueprint - you can use native calibration instead of generic, and the automation will handle the calibration offset automatically.
Is it possible to set a schedule locally on the w500 using HA via zigbee2mqtt? I want to avoid running schedules on HA to remove the dependency on HA running for schedules.
Just trying to figure out what is exposed to HA using the slzb-06p7.
Nope, it’s not possible
{
"child_lock": "LOCK",
"energy": 24.42,
"humidity": 50,
"hysteresis": 0,
"last_seen": "2026-02-04T23:39:37.370Z",
"linkquality": 66,
"local_temperature": 21.87,
"local_temperature_calibration": 0,
"max_heat_setpoint_limit": 30,
"min_heat_setpoint_limit": 5,
"ntc_sensor_type": "unknown",
"occupied_heating_setpoint": 22.5,
"power": 995,
"preset": "manual",
"running_state": "heat",
"sensor": "internal",
"state": "idle",
"system_mode": "heat",
"temperature_setpoint_hold": false,
"temperature_setpoint_hold_duration": 0,
"window_detection": "OFF"
}
Maybe dumb question but why you just don’t use NTC sensor? I have mine wired and have set a limit to 30 degrees Celsius, works great. I have external wireless sensors set at actual level (~150 cm from the ground) to know the actual human felt temperature. Also, having an external sensor on the floor is not the same as having a sensor inside a floor, so please be aware of cracking your tiles (mine broke with previous thermostat)
Oh yes I was debugging this max_heat_setpoint the whole yesterday…
No way to open up the device, it freezes the UI and have to reload the web page.
So the quirk fixed to incorrect max_heat_setpoint issue?
How well does the Aqara M100 (I assume it’s Matter protocol?) work?
I was thinking of adding some new devices (IKEA has this air quality monitor that works with Matter) and my current Zigbee works with the Sonoff zigbee receiver.
My floor termostat is only showing consistantly -0.010 C, if anyone know how to fix it I’m open for suggestions!
Yes, completely fixed the HA web interface from crashing.
I’m not using it anymore. It was acting as a Zigbee to Matter-over-Wifi gateway, and worked well enough, but didn’t expose all the functionality through Matter. For me, it was better to bypass the M100 and connect HA directly to the W500 via Zigbee. I don’t have any other matter-capable devices. The new IKEA stuff is Matter over thread, so I guess it should work okay, but I’ve not tested.