Aqara W100 sensor/thermostat — temperature and humidity sensor Zigbee Matter Thread

[_Will_71]

According to the zigbee2mqtt documentation:

Aqara TH-S04D control via MQTT | Zigbee2MQTT

Here’s how to send a zigbee2mqtt message

topic = zigbee2mqtt/FRIENDLY_NAME/set
payload = {« external_humidity »: NEW_VALUE}

and in Gladys:

If that works like this then replace the 38 with a variable.

You can also check with a tool like MQTTX or MQTT Explorer if your message is being sent properly

[_Will_71]

And maybe you also need to change this setting in zigbee2mqtt:

[bjm]

Got it @_Will_71 I have a 38° showing

It was too good — I replaced the 38 with the variable and it still shows 38.

[bjm]

Here is the correct formula:

{"external_temperature": "
1.1. ref-temperature-sb-chambre-6 (ref-temperature-sb-chambre-6)
"}

![Screenshot from 2025-05-26

[bjm]

I have a strange issue.
My Counter that increments the reference temperature of my W100

[mutmut]

I think it’s your trigger that’s causing this.
If the temperature of your W100 changes (even 0.1°C) then your scene is triggered.
In my opinion you should delete your Telegram verification message, otherwise you’ll be spammed.

[bjm]

No, actually the scene only triggers if I press the + button or if I change the value directly on the dashboard.
The counter was stuck at 35 since last night (maximum value) and I didn’t reset it.
It’s as if the value had been erased from Gladys’s memory and reverted to 1, the minimum value I set in MQTT > Devices > ref-temperature-sb-chambre-6
So I wanted to check « Keep state history » and when I saved it I got Error: the device is misconfigured.
After 3-4 attempts I managed to save (without changing anything).

[pierre-gilles]

@bjm

No, actually the scene is triggered only if I press the + button or if I change the value directly on the dashboard.

There must be a logic problem in your scenes, share all your scenes with us here and we’ll help you

[bjm]

Unbelievable, customers have just rung the doorbell and once again the counter switched to 1.

my doorbell is 433 MHz so with Node-RED and RFLink and Gladys it sends me a Telegram notification that I receive on my phone

It’s true that I had also tried to send the value to the W100 via Node-RED, but I erased everything.
I should have a backup, I can try to reinstall it.
My counter scene is still identical to post No. 38

[bjm]

Reinstalled Node-Red backup: ineffective.
Deleted the device ref-temperature-sb-chambre-6 and recreated it: ineffective.
Finally I added a new feature to my device ref-temperature-sb-chambre-6.
This time I chose Temperature
And as the ID I added a small B to it
mqtt:ref-temperature-sb-chambre-6B
Modified all references in my scenes and oh miracle the doorbell no longer resets the counter to 1
And I removed setpoint temperature.

[bjm]

Video in preparation.

[bjm]

[bjm]

Thank you all for your help.

[pierre-gilles]

Thanks for this video tutorial @bjm, it’s very thorough

You say the W100 doesn’t always send the latest measured temperature value — I wonder if it’s because your W100 is a bit far from a Zigbee repeater node; I see the signal strength is really weak on your dashboard

If you can put a smart plug or a bulb between your W100 and your Zigbee USB stick, it can help

[mutmut]

Congrats on setting all this up @bjm, great job!
Same remark as @pierre-gilles about your signal — a repeater wouldn’t go amiss.

Regarding the temperature reporting, I saw in your config that it was based only on the temp threshold at 5°C:

That means the W100 only sends you the new value if it’s more or less than the previous one by 5°C, not ideal.
I’d choose threshold_period as Temp report mode, set the Temp period to 60 sec and the Temp threshold to 1°C or 0.5°C.
The lower it is the better, but the batteries won’t appreciate it.
That way if the temperature changes by 1°C (or 0.5°C) in less than a minute, you’ll get the update immediately.

Same for humidity. At my place I control the mechanical ventilation (VMC) to turn off at night (motor slightly audible) and I restart it in the morning at 7:15. But if there’s too much humidity (>75%, SNZB-02D probe) from 6am in the bathroom (a slightly long shower) then I reactivate the VMC before the scheduled time.

You should check what Sampling and its Period correspond to, and maybe also adjust the High and Low values so you receive alerts (even if you have safeguards in your scenes).

[bjm]

When I saw that it couldn’t connect, I installed a repeater on the landing 3 meters from it.

But it won’t connect.

[guim31]

Of all my past attempts, I have never managed to force a device to connect to a router.
However, over time the device connects « by itself », I imagine it makes attempts at regular intervals.

[pierre-gilles]

@bjm

@pierre-gilles do you want to retrieve the video to put it on Gladys’ YouTube channel?

It’s great on your channel Can I share it on social media?

[bjm]

@pierre-gilles

It’s very good on your channel Can I share it on social networks?

Yes, you can without problems

[bjm]

A quick follow-up on the W100.
Twice I had to remove the batteries because the dial display was always stuck on the same number.
This summer, I noticed a problem in my scene: the radiator turns on then turns off 9 seconds later, so with the cold coming I tried to debug the scene with Telegram messages.
and when I got to the w100 I found this

Zigbee still works but anyway it really isn’t very reliable.
So it wasn’t a scene problem, it was the Nodon module that had switched to pulse mode 10000ms
![Capture d’écran du 2025-10-02 20-02-43|690x99](upload://bMz56LUuDCgraTzaD