Aqara W100 *NEW Update available*

[gtxteo]

Hi everyone @AqaraOfficial @AqaraBot today in Germany is a new update available for Aqara W100 under Zigbee connection.

Current Version: 0.0.0_1437
Latest Version: 0.0.0_1539

[AqaraBot]

@gtxteo That’s really great news! Thanks for sharing this valuable information about the new update for the Aqara W100 in Germany under Zigbee connection. It’s always exciting to see product updates that might bring in new features or improvements. Have you installed the update yet? If so, we’d love to hear about any differences or new experiences you’ve noticed. If you have any suggestions or recommendations for improvement, you can submit feedback manually through customer service.

[harry_k]

what has changd in the update? Are there some informations?

[jamesy305]

Thanks, I’ll give it a go on one of my displays and see how it goes. Really wish there was a way to track firmware updates and changes.

[gtxteo]

Sorry, no chancelog available.

[gtxteo]

I hope the issue of disconnection from valve E1 after some time has been resolved.

[Dmitriy_Y]

Added W600 support

[avram_bv]

A tip… I had problems with the update. Two out of three devices failed to update after many attempts. The problem was solved by removing the batteries and reinserting them.

[AqaraBot]

@avram_bv Thanks so much for sharing this troubleshooting tip! It’s really valuable for others who might encounter similar issues during the Aqara W100 update. Battery-related problems can often cause firmware update failures, and your solution of removing and reinserting the batteries is a great approach.

For those who face firmware upgrade failures in other Aqara devices, here are some general points to confirm as well:

1. Ensure your device and gateway have good communication. Before upgrading, click on the device once to ensure the gateway indicates a normal connection, or control the device in the app. If normal, then initiate the upgrade.
2. For battery-operated devices, check if your device has sufficient battery. If the battery is too low, it might cause the firmware upgrade to fail, so recharge or replace the battery and try again.
3. Ensure you are using the latest version of the gateway and APP for the upgrade.
4. Try restarting the device and the router and attempt the firmware upgrade again.
5. Try re-entering the sub-device into the network and then attempt the upgrade again.
6. If all above methods fail, we recommend contacting our customer service for further assistance and support.

If you have any other experiences or tips to share in the future, don’t hesitate to post them. And if you have any suggestions or recommendations for improvement, you can submit feedback manually through customer service.

[nzjrs]

Unfortunately the update did not add an automation trigger for temperature above / below the setpoint as I have been requesting for months

@XianTangHE @AqaraOfficial

[XianTangHE]

@Harold

[danergo]

Hi!

Can we hope for adding support for reporting 0.5 degree “occupied_heating_setpoint” in zigbee mode?

Feels uncomfortable setting to 24.5 °C, and getting 24 for this item.

Moreover buttons feels way too slow: when I push one button it takes about a second for the w100 to react.

I know this is handling a lot, but buttons need to be prioritized over pretty much anything else if you really keen on keeping customers.

@gtxteo: do you happen to have any updates regarding this?

Thank you!

[ludovic_boue]

This seems a little off topic in relation to the October update.

[danergo]

I posted here, because nowhere found anyone replying…

But I luckily found a solution: get refund and buy a better thermostat from reputable European brand like Bosch or Siemens.

[gtxteo]

Hi, my set point is set to a change of 0.5 via custom setting in ZigBee mode. I have no problems with this. If you want I can share screenshots of my settings on the W100.
After these changes of my W100’s custom settings, connected to my E1 valve I have no temperature problems. If imposed 22.5 resulted 22.5. Also tested with other sensors. Thanks to the @gafich10 tutorial I no longer have any kind of problem. Obviously I set the device up to my needs.

[danergo]

Im trying to use this with Z2M.

Please see details here:

W100 zigbee firmware inconsistencies

Hi The W100 could be a great product but it has some issues that need to be solved with the Zigbee firmware update asap. in thermostat mode, the W100 allows 0.5° steps. But the zigbee endpoint handling the PMTSD frame containing this value only send and receive plain integer value. This is a big issue that need to be adressed on a firmware update. we should be able to set the thermostat mode precision. My HVAC here use 0.1° precision, I’d like to be able to use 0.1° steps from the W100 there…

[gtxteo]

I think doesn’t work not natively.

With Aqara W100 (thermostat) connected to Zigbee2MQTT, the heating setpoint (occupied_heating_setpoint) does not support 0.1 °C steps.
This limitation is imposed by the Aqara firmware, not by Z2M.

Technical details

Heating setpoint
→ minimum step 0.5 °C (e.g. 18.0 – 18.5 – 19.0)

Temperature calibration (local_temperature_calibration)
→ supports 0.1 °C, but it is not the setpoint; it is only used to correct the sensor reading

Zigbee2MQTT correctly exposes the entities, but cannot force a resolution not supported by the device

Possible workarounds

If you need finer control (0.1 °C):

1. Use a “virtual” thermostat (e.g. in Home Assistant)

2. Control the Aqara W100 with ON/OFF automations based on a 0.1 °C threshold

3. Use an external temperature sensor plus custom PID or hysteresis logic

Practical example

Virtual setpoint: 21.3 °C

Aqara set to 21.5 °C

Automation that turns heating on/off based on the actual temperature.

I searched for information around and found that this is the only possibility to do what you want.

[gtxteo]

Possible solution:

System setup

Home Assistant as the main controller

Zigbee2MQTT for Zigbee integration

Aqara W100 firmware: 0.0.0_1539

Device type: Thermostatic radiator valve (TRV)

---

Aqara W100 (Z2M settings)

Set these once and leave them fixed:

system_mode: heat

occupied_heating_setpoint: 25 °C
(high value to prevent local control from interfering)

temperature_calibration: adjust if needed (0.1 °C steps supported)

Do not use local schedules or change the setpoint dynamically

The W100 is used only as an actuator (open/close valve).

---

Home Assistant logic

Recommended: Better Thermostat (HACS)

Controls the room temperature with 0.1 °C resolution

Uses:

External room temperature sensor

Aqara W100 as the TRV

Enables:

PID control

Smooth valve behavior

Reduced temperature oscillation

Set target temperature step to 0.1 °C.

---

Alternative: Generic Thermostat

climate:

• platform: generic_thermostat
  name: “Room – Virtual”
  heater: switch.w100_valve
  target_sensor: sensor.room_temperature
  target_temp_step: 0.1
  cold_tolerance: 0.1
  hot_tolerance: 0.1

---

Key concept

Home Assistant decides when to heat

Aqara W100 only executes commands

The native 0.5 °C setpoint limit of the W100 is completely bypassed

Effective temperature control at 0.1 °C

---

Best practices

Use one external temperature sensor per room

Disable or ignore W100 internal scheduling

Let Home Assistant be the only control logic

[gtxteo]

I hope it can help

[danergo]

My problem is:

On w100 i set the required temperature to 24.5, and it is reported as 24 in z2m.

I can select temperature in 0.5 degrees on w100 but it reports it as integer. So if i set it to 24.0 or 24.5 on the w100, it reports it as 24 in both cases.