Aqara Thermostat W500

Developer Hub
,
1

Subject: Issue with Aqara W500 Thermostat – Cannot Access Settings or Firmware Update

Dear Aqara Support,

I recently added an Aqara W500 thermostat to my Aqara Home setup using the Aqara Hub M3. The thermostat was successfully added to the app and also appears in Apple HomeKit. However, I’m experiencing the following issues:
• The thermostat cannot be turned on or controlled via the Aqara Home app.
• I cannot access any advanced settings for the device.
• There is no option to update the firmware from within the Aqara Home app.
• The device is visible in Apple Home but limited in function.

I have tried removing and re-adding the device, resetting it, and restarting the hub, but nothing helped. Unless a solution is found, I plan to return the product this weekend.

Can you please help me resolve this issue?

Thank you,
Robert

1 Like
2

Good evening, update the app and hub to the latest version, and try to remove and add w500 again.

1 Like
3

This is EU version, maybe it doesn’t work in mainland China, please select country from European region and it will work.

2 Likes
4

Are you sure you have Zigbee enabled? If not, then there will be restrictions.

IMG_20250717_233820
IMG_20250717_2338201080×2340 389 KB

5

The video shows that the w500 is connected via zigbee

6

Yes, exactly, it’s the EU version and unfortunately it doesn’t work in mainland China due to these regional restrictions from Aqara. These limitations are really starting to annoy me, so I’d rather return it to the store.

7

Hi, I solved it by switching everything from Aqara to the EU zone and everything works now. Thank you all for your help. Robert

1 Like
8

I’m glad I was able to help you, have a nice day.

1 Like
9

Plz add support for 12k ntc sensors

10

Hi, I’ve been using the W500 thermostat for electric floor heating for about 3 months. While the hardware looks great, I have two major issues compared to my previous Meross thermostat:

  1. Floor Sensor Compatibility (Beta Value)

I have a legacy floor sensor embedded in concrete/tiles from a previous installation (Meross). It is a standard 10kΩ sensor, but with a Beta value of 3380 (Aqara seems to require 3950). Since I cannot rip up the bathroom floor to replace the sensor, the readings are unstable/jumping.

Suggestion: Please add a software setting to adjust the Beta value of the NTC sensor (or at least support Beta 3380), as many users are upgrading from other brands and cannot replace embedded sensors. I am currently forced to use the internal air sensor only, which is not ideal for floor heating.

  1. External Window Sensor Integration

I am unable to directly link my Aqara Door & Window Sensor to the thermostat to trigger the “Window Open Protection” mode.

The thermostat is installed in a bathroom where we ventilate frequently after showering. The internal “temperature drop detection” is not reliable enough. I need the thermostat to turn off immediately when the Aqara Window Sensor reports “Open”. It is disappointing that two Aqara devices do not work together natively for this feature.

Overall, I was happier with the functionality of my previous Meross thermostat. I hope a firmware update can address these issues soon. Robert

4 Likes
11

Same issue here. Existing floor sensor (100k) and temperature is flapping with ±3C every second making it unsable.

Tried the supplied 10k sensor (just connecting it) and it flaps between 0.4C every second.

This must be fixed.

12

Hello, welcome to the forum. Did you definitely switch to the NTC sensor? The native sensor does not give such oscillations, check, maybe you did not switch to NTC and the external W500 sensor works? Please check.

If there is still a problem with the NTC sensor, I recommend contacting support.

2 Likes
13

Yes, I have fiddled with all settings to try to make my 100k sensor work, it reports values 19-22 every second. So having temperatur set to 21 it just contantly turns on/off.

I created a support ticket, just as others did https://www.reddit.com/r/Aqara/comments/1mfigqw/comment/nh78r02/

3 Likes
14

I want to clarify, resistance is only one component, the NTC sensor must have a 3950 curve, in your case, other curve parameters may have been set, which leads to temperature inconsistencies.

2 Likes
15

“other curve parameters have been set” - how so? The sensor is built into the floor and not very easy to replace, so it is what it is.

as above, also asking to make it possible to adjust beta value.
I would assume either software or ripping out the sensors from floors are the only solutions then?

2 Likes
16

And you didn’t consider the possibility of pushing the native sensor from the W500 into the embedded pipe. The wire in it is quite solid, you can push it in at the same time without pulling out the old one. I managed to do it.

1 Like
17

Yes, I’ve done that now, but I’m not sure exactly where it is measuring (maybe in the wall :wink: old sensor is “stuck” in the floor.
Even with the default 10k sensor, the readings are super sensitive, just with much smaller values. 21.7, 21.9 22 21.7.
I assume when using 100k the factor makes the flapping larger.

I have a different zwave thermostat that is super stable.

18

Hello, this should not be the case with the native Aqara sensor. Contact support, you may have a problem with the W500 or a faulty NTC.
By the way, have you checked whether the temperature jumps simply with the Aqara sensor connected indoors (not on the floor)?

19

Thanks.

Yes, the internal sensor is stable.

20

I’m talking about NTC being on the surface (not in the floor). As it shows, is it jumping?