Aqara W100 Blueprint for Thermostat mode

Blueprints Exchange
, , ,
1

This blueprint handle bidirectional synchronisation between Aqara W100 in thermostat mode and a climate entity.

It is intended to be used with Zigbee2mqtt.

Important:

For Z2M < 2.7.0 you need to install this external converter first:

It exposes natively a virtual climate entity compatible with HA.

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Features:

  • sync from climate entity to w100
  • sync from w100 to climate entity
  • configure features: hvac mode available ( cool, heat, auto ) , fan mode
  • publish external temp/hum data to w100
  • prevent the w100 hvac mode to be set in a mode unsupported by the real climate entity.
1 Like
2

Thanks for your great work. Heating works great
Is it possible to add the possiblity to add separate(s) devices for cooling / fan, too?

I have a floor heating which works great with your blueprint. But cooling is done with a separate Climate device.
So I like to control two different climate devices.
It would be great if I can control both with the w100.

again thanks a lot for your work.

3

Is this dependent on owning an AQARA hub or will ZBT1 zigbee controller suffice?

4

If you are running z2mqtt on your ZBT1 it is sufficient

5

@chrisExh It is made for Zigbee2mqtt, you need to use the provided converter.

@boldie , no it’s made to synchronise 2 climate entities, but you can easily edit the blueprint and customize your automation with your needs.
Or make a template to fusion your 2 climates entities in one.

6

Thank you so much. Works like a charm.
But beware, that the .JS file needs to be located in /zigbee2mqtt/external_converters/

1 Like
7

Hello,
I am looking for a way to retrieve Child Look information (two buttons pressed) in Home Assistant.
My goal would be to be able to disable the automations that control my air conditioning and switch to manual mode. Of course, I only need this to work in one direction, from W100 to HA.
Any ideas are welcome.

Merci :wink:

8

I don’t think the device publish the child lock state.
Seems it’s only a lock to the button without any cluster reporting it.

9

I haven’t seen anything like this in mqtt, and I’m searching and thinking that something might be possible with an external converter to notify that the setpoint change comes from the W100 in order to disengage my automation…

10

It looks like w100 has a setpoint steepness of 0.5 per click, while the climate.w100 component created works on a steepness of 1.0.

11

It is from the device firmware. The device only send and accept integers value.
But the device stupidly allows 0.5 steps on the screen.

I hope they will fix this in a future firmware. Either display integers or allows floats values on their PMTSD protocol ( better )

You can open a support ticket for that. If we all ask perhaps they will listen.

1 Like