Aqara Floor Heating Thermostat W500

[lkoen]

Is there already an existing issue for this?

• I have searched the existing issues and there is none for my device

Product name

Aqara Floor Heating Thermostat W500

Manufacturer

Aqara

Model identifier

lumi.airrtc.aeu001

Device type to add

Thermostat

Node info

Endpoints and clusters

Basic

Further relevant clusters

Lumi Specific

Relative Humidity

Temperature

Power Configuration

On/Off

Level Control

Color Control

Thermostat

Simple Metering

Electrical Measurement

Any other cluster of relevance/interest

[lkoen]

There are threads with support on ZHA and Z2Mqtt:
Koenkk/zigbee-herdsman-converters#9616
zigpy/zha-device-handlers#4412

I have created a first version of a DDF file, largely based on the ZHA quirk (see link above):
lumi.airrtc.aeu001.json

What currently works:

Reading: Temperature, Humidity, Child Lock, Preset, Valve state (on/off), Power (not sure about the unit though), Offset (unverified), Window Open (unverified)
Reading/Writing: Heatsetpoint
Writing on Preset, Child Lock, Offset, might work but has not been tested.

What is currently missing:
0x0280 (sensortype)
0x030C (hysteresis)
0x0315 (ntctype)
Not sure about consumption

Although I've put them in the DDF they don't seem to appear on the device. I can't even see those in the lumi cluster, but then again there are no values in the 0x300s range, but 0x311 (preset) still works fine...

[Smanar]

He ... you have used IA ? Because lot of comment on the DDF

Although I've put them in the DDF they don't seem to appear on the device

Do you realy need them ? Because there is some setting that can be useless ?
Else if you relay need them (if there is no filed that can be used) you need to create new json in this folder https://github.com/dresden-elektronik/deconz-rest-plugin/tree/master/devices/generic/items

For exemple
config_hysteresis.json

{
  "schema": "resourceitem1.schema.json",
  "id": "config/hysteresis",
  "datatype": "UInt8",
  "access": "RW",
  "public": true,
  "default": 0,
  "description": "xxxxxxxxxxxxxxxxx."
}

And restart deconz, at next restart you will be able to use them.

[lkoen]

He ... you have used IA ? Because lot of comment on the DDF

I used it to create a first version and then did some manual tweaking. Not sure what you mean with comment, but maybe you can help me to clean up the DDF accordingly?

Do you realy need them ? Because there is some setting that can be useless ?

Personally, I don't need them, but for someone who wants to use the external sensor that comes with the thermostat, setting the sensortype is essential.

I tried adding the config files as you suggested and now I see the values. However, I always only get the default value, so I am not sure if it is really working. At least ntctype should give a non-zero value.

Sadly I currently don't have the time to dig deeper into this. Maybe you can just add support with the things that are already working for now?

[Smanar]

Sadly I currently don't have the time to dig deeper into this. Maybe you can just add support with the things that are already working for now?

Sure, it's your DDF, you can put that you want.
If it's working for you, it's fine, but I m sure others devs will found problems on the actual DDF.

For exemple about my comment.

• "status": "Silver" can use "gold", I m not sure there is more than 3 DDF with silver.
• in "out" and "in" Endpoint, can use only the one used in the DDF.
• There is no "eval" par for "config/mode", so this one can't work.
• What is "config/offset" for you ? If it's just a temperature offset, there is a better way to do that, but without "eval", this one will not work too, if it's a thermostat setting can take a look on the "devices\bosch\room_thermostat2.json"
• "config/locked" I have big doubt using "unlocked" or "locked" will work, I think 0 and 1 will be fine (this field is bool type)..
• "config/preset" will not work as it too, you are too optimistic on the "values" part work ^^
• I have doubt on the min/max for the 0x001c bind/report.
• "state/on" in the ZHAtermostat haven't the same fonction than in a "light" entry (valve state<>toogle device), I think it will be better to create a "light" entry to manage the 0x0006 Cluster.
• From my memory Cluster 0xfcc0 don't need bind/report.

Instead of using IA that make crap with random code, just take a look for exemple in

• "devices\bosch\room_thermostat2.json"
• "devices\xiaomi\xiaomi_lumi.airrtc.agl001.json"

And just copy paste the code you need, it's just what IA are doing, but for that you can do better than them without problem, if you have take information on the ZHA quirk you are able to understand thoses 2 DDF.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.