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’s no calibration feature exposed calibrate for Temperature and Humidity sensor. I see 0.8° difference between my lab calibrated temperature sensor and the W100. Any T°/Hum sensor needs a way to be calibrated as they will drift over time. Most cheap zigbee sensors on the market have this as it’s mandatory.
Are the moderators here forwarding issues and features request to aqara development team ?
I’ve tried to contact technical support, but they don’t even understand what I’m talking about…
Hello, welcome to the forum. These settings are in W100. Sensitivity can be set from 0.2 °C, polling period (external display 0.5 seconds, data exchange period with the gateway 10 seconds. I made a description of these settings in this topic. W100 Explanation of the temperature sampling setting для то
Note, the W100 is a thermometer, not a thermostat. It can be used as a remote control and monitor for the W500, W600 and E1.
I know it’s not a thermostat, but it can be used to control a thermostat.
I shouldn’t have to explain that
That’s what I mean , the w100 in zigbee firmware has 2 modes, normal mode and thermostat mode.
In thermostat mode, it then display the middle line with HVAC info ( heat/cool/… and Fan mode ) , then the hardware buttons are only used for thermostat mode ( no more zigbee Actions ) .
When pushing the up/down button, it then increase/lower by 0.5° step the virtual thermostat setpoint. And then send the value using a PMTSD frame like this:
YYYY-MM-DD HH:mm:ss_Px_Mx_Tx_Sx_Dx
Tx is the temperature setpoint sent, and it’s always only a float value.
( If the w100 is set to 19.5 °C, it then only send on the PMTSD T19 instead of T19.5.
And same on the other side, if the thermostat ( the real one ) send T19.5, W100 will only get 19° and skip the float.
This has nothing to do with calibration.
The zigbee firmware should have an endpoint to set an offset to the temperature and humidity value.
There’s no other way to do it.
Hello, now I understand what you asked.
Regarding 0.5 °C, Aqara currently operates only with these settings (unfortunately).
Regarding the thermostat mode, I cannot say for sure that the temperature is set without being tied to an external thermostat (I have not checked this). I will do some research when I get home.
At one time, we raised a whole topic on the issue of a virtual thermostat so that temperatures can be set directly in automation from W100
I use it already with an external thermostat. I had to reverse how it work internally first. That’s how I’ve found this flaw.
The most important problem here, is the W100 sending only integer values instead of float. We can live with just a 0.5° precision, but this integer vs float issue is really troublesome.
Also the calibration in any good T°/Hum sensor have a way to set an offset, it’s a mandatory feature or the device will be good for trashbin after few monthes when it drifted too much to be acceptable.
All sensors on the market drifts over time, + factory calibration is not always good.
