Coolo CS-201Z Soil Moisture Sensor

[umtauscher]

This sensor is working only partially.
The water_warning entity is always reported as NULL
Does anybody have this working properly?

I have other sensors with ZG-303Z that look identical from the outside working correctly.

[Nisbo]

I have 2 x CS-201Z and both have the same issue than you. Additionally the update of the Soil moisture happens only after several hours. Interval is set to 30 seconds. Update of temperature is working fine.

[13717033460]

Moisture is collected every 30 seconds by default, but information will only be uploaded when there is a 5% change

[13717033460]

You can test it by inserting the product into soil (or water), waiting for 30 seconds to see if there is any uploaded information, and then pulling out the product, waiting for 30 seconds to see if there is any information

[totopesce]

I have the same problem, only temperature seems to work. Humidity shows very high values, moisture shows 0 and battery shows 100 even with rechargable batteries that are not topped up.

[13717033460]

If it is still 0% in water, then it is a defective product

[Koenkk]

@13717033460 something seems to be wrong with the integration, could you check this?

[13717033460]

Sorry for the mistake in writing the data type， [106, "dry", tuya.valueConverter.trueFalse0], Need to be modified to [106, "dry", tuya.valueConverter.raw].

[wenzelt]

same here

[reflix299]

I experience the same issues. Especially moisture is not updating, only when the button on device is pressed. This also happens if the change of moisture is significantly larger than 5%.

[13717033460]

You can test it by inserting the product into soil (or water), waiting for 30 seconds to see if there is any uploaded information, and then pulling out the product, waiting for 30 seconds to see if there is any information

[reflix299]

When reviewing the sensor data, I have multiple cases, where I have constant moisture of multiple hours and the value changes suddenly to a value >> 5% difference. That seems to me like a bug in the value reporting.

Additionally, will any update be made available via OTA (so far it seems to not support OTA via Z2M), or is a hardware update/replacement required?

[JoshWobbles]

My log is full of error from these
zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds

zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped

[JoshWobbles]

@13717033460 any ideas about this one?

[R3ITOSv87]

[13717033460]

You can test it by inserting the product into soil (or water), waiting for 30 seconds to see if there is any uploaded information, and then pulling out the product, waiting for 30 seconds to see if there is any information

[13717033460]

In order to save power consumption, The current version requires a 5% difference in soil moisture before uploading, and we will change it to 3% in the future.

[13717033460]

It samples every 30 seconds to compare the soil moisture content. If the difference is greater than 4%, upload the moisture value

[MSL-DA]

It samples every 30 seconds to compare the soil moisture content. If the difference is greater than 4%, upload the moisture value

Stop repeating your battery-saving mantra. We don’t care about power consumption here.

Users need reliable updates on a fixed schedule, regardless of moisture change. We need a fresh value every 5 minutes or so, period.

Your “only if delta >5%” logic completely misses the point.

Please either acknowledge the flaw or suggest a real fix. Otherwise, don't comment.

That attitude won't get you far.

[umtauscher]

"Users need reliable updates on a fixed schedule, regardless of moisture change.
We need a fresh value every 5 minutes or so, period."

well, I beg to differ.
How much difference in soil moisture do you think in 5 minutes could be measured?
When I water my plants, it takes many days until significant changes can be measured.
Minimizing battery consumption is the right way to go.

I can see, how this makes debugging a faulty sensor more difficult, but that's not normal operation.
If you take the advice how to check a certain sensor your good to go.
Cheers

[JoshWobbles]

I dont mind a slow update, but mine haven’t updated in several days even after heavy rain despite good signal and good temperature updates. I think the errors and ignored frames listed above are partly to blame.

[13717033460]

Thank you for your suggestion. We have changed the firmware to have a moisture error of 3% and will upload it immediately. If there are no other changes, we will also upload moisture data at least once per hour.

[13717033460]

[Nisbo]

This is a diferent chipset which is irrelevant for the initial problem

Where do you see the chipset ?

[Nisbo]

How can we update the firmware via Zigbee2Mqtt ?

[umtauscher]

I‘m sorry, I was confused.
I deleted the remark about the different chipset.

I doubt that this device is updateable via ota.

[zeliorite]

Newbie question: how do I update the firmware? I don't see OTA support for this device. Thanks in advance.

[Polder443]

@13717033460 can you please explain us, how to update the firmware?

[totopesce]

@13717033460 any update on the fix?

[totopesce]

@13717033460 any update on the fix?

[priest1111]

Is there any information on how to update the fimware, thanks 🔢

[Stevenva007]

I would also like to know!

[ChipwizBen]

I have 8 of these sensors. 7 of them update when they feel like it, which is about once a week, despite some going from dry to drenched.

One of the sensors updates every minute, even when placed directly next to another in the same plant that takes days or weeks to update. There is something fundamentally broken with this firmware.

Sensor every minute:

One of the other seven:

I have brought one into my office to try to work out the difference between the sensor that updates regularly, and one that does not:

I've also started grouping the others to work out the variation in readings, which is massive (60%+ sometimes):

I've concluded that these sensors are total rubbish. They neither reliably check in (even with major changes in moisture), and when they do check in the values are so different that they are untrustworthy.

[ChipwizBen]

Some more observations that don't align with what @13717033460 was suggesting. This one hyper-active sensor is checking in several times a minute, all with the same values. These broadcasts are 1, then 10 seconds apart, with identical values for moisture / temperature:

info 2025-07-30 15:40:09z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Living Room Philodendron', payload '{"battery":100,"dry":false,"humidity":84,"humidity_calibration":0,"linkquality":83,"soil_calibration":0,"soil_moisture":23,"soil_sampling":30,"soil_warning":20,"temperature":17,"temperature_calibration":0,"temperature_sampling":30,"temperature_unit":"celsius"}'
info 2025-07-30 15:40:10z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Living Room Philodendron', payload '{"battery":100,"dry":false,"humidity":84,"humidity_calibration":0,"linkquality":87,"soil_calibration":0,"soil_moisture":23,"soil_sampling":30,"soil_warning":20,"temperature":17,"temperature_calibration":0,"temperature_sampling":30,"temperature_unit":"celsius"}'
info 2025-07-30 15:40:21z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Living Room Philodendron', payload '{"battery":100,"dry":false,"humidity":84,"humidity_calibration":0,"linkquality":83,"soil_calibration":0,"soil_moisture":23,"soil_sampling":30,"soil_warning":20,"temperature":17,"temperature_calibration":0,"temperature_sampling":30,"temperature_unit":"celsius"}'

[Nniccollas]

Any news about How to upgrade the Firmware. Upload moisture sample once per hour is the good approach.

[Nniccollas]

@Koenkk Is it possible to exclude temporarely the device from the supported list? Till the issue is solve… This morning, need to press the physical button to get upload datas in Z2M….

[umtauscher]

What good would that do? Mine work perfectly. Just because you seem to have a malfunctioning batch?

[Nniccollas]

Perfectly? You are the author of the thread. If your water warning is Null, that doesn’t work as expected. Easy to found also a lot of claim from the web shop merchand.

[umtauscher]

Yes perfectly is a bit exaggerated. :-)
Nevertheless Water warning is a cosmetic problem.
You can always check the percentage.
I don‘t think unsupported is a bit too much.

[FroggyRZE]

I have 3 of these devices since a few weeks, Firmware Date is 20250709. It seems for me they do work fine. The value of soil_moisture is broadcasted immediatly when I water my plants.

I only worry about water resistance of these devices when used outdoors.

[FroggyRZE]

I see more details on this page.
Zigbee2MQTT-Version 2.5.1
Frontend-Version 0.9.16

Do you use an older version?

[Nisbo]

I see more details on this page. Zigbee2MQTT-Version 2.5.1 Frontend-Version 0.9.16

Do you use an older version?

Zigbee2MQTT version
2.6.0
Frontend version
1.5.2

EDIT:
even if I switch to the old frontend
Frontend-Version 0.9.19
no version date is shown.

[FroggyRZE]

Do you use the windfront frontend package?

[Nisbo]

Do you use the windfront frontend package?

I tried both

[FroggyRZE]

I just realized that only 2 of 3 sensors show the date, 1 sensor does not.

[Polder443]

Does anyone know how to update? I received three new ones, and they work much better.

[doenermann]

I have firmware build 30072025. Still reporting once in a while and then suddenly stops reporting soil moisture... For now I can not recommend buying these.

[FroggyRZE]

It seems that it only works one-way after a while. When watering the plants, it goes up to for example 87% and stays there. With more water it ends at 100% and stays there.
There must be a big bug in the firmware.

[doenermann]

stupid question: who is editing the firmware and does an update over zigbee work in general?
Firmware is probably closed-source so the manufacturer is needed?

[ntnmrndn]

Worked for a while and then stopped reporting any change of moisture :/

[wenzelt]

Same here

[ntnmrndn]

Ok; it seems to mysteriously have been fixed...

[doenermann]

My sensor is showing 100% for more than a week now.. does not seem to be correct to me. But getting no answers concerning this problem from the manufactures says enough for me... 100% don't buy.

[doenermann]

Is anything happening here?
@13717033460: as you seem to be some kind of product related guy: are you working on the firmware? What are we supposed to to with our devices?

[zeroy99]

I just bought one and Soil Humidity just does not report at all - The device appears with firmware 0126082025, is that right? No ZigBee2MQTT Ota update avail. Setting Soil Humidity calibration to max of 30 will make the Soil Humidity to be 30% - is the issue with the device or with the HA/Z2MQTT Integration??

[13717033460]

There is no moisture data even when it's placed in water, and no data appears when the button is pressed once. Then it must be broken. 发自我的iPhone

…

------------------ Original ------------------ From: ZeRoY ***@***.***> Date: Mon,Nov 10,2025 8:27 PM To: Koenkk/zigbee2mqtt ***@***.***> Cc: jomders ***@***.***>, Mention ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] Coolo CS-201Z Soil Moisture Sensor(Discussion #27830) I just bought one and Soil Humidity just does not report at all - The device appears with firmware 0126082025, is that right? No ZigBee2MQTT Ota update avail. Setting Soil Humidity calibration to max of 30 will make the Soil Humidity to be 30% - is the issue with the device or with the HA/Z2MQTT Integration?? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zeroy99]

After putting the device in a glass of water the Soil Humidity shot up to 171% - Took it out, dried it and placed into soil, I now get 100% - which seems to be valid as the soil is quite wet. The Alert for dry however is activated and shouldnt as it is set to 20% Soil moisture? Anyway to update firmware then? Last question I do not see a "button" to press?

[13717033460]

The maximum water content is 100%, there will be no 171%.  发自我的iPhone

…

------------------ Original ------------------ From: ZeRoY ***@***.***> Date: Mon,Nov 10,2025 8:55 PM To: Koenkk/zigbee2mqtt ***@***.***> Cc: jomders ***@***.***>, Mention ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] Coolo CS-201Z Soil Moisture Sensor(Discussion #27830) After putting the device in a glass of water the Soil Humidity shot up to 171% - Took it out, dried it and placed into soil, I now get 100% - which seems to be valid as the soil is quite wet. The Alert for dry however is activated and shouldnt as it is set to 20% Soil moisture? Anyway to update firmware then? Last question I do not see a "button" to press? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[doenermann]

What about the older devices which stop reporting soil humidity after a couple hours/days completely? Will there be an update or are they wasted money and garbage now?

[zeroy99]

I am clearly seeing values above 100% - would you say the device is faulty?

[13717033460]

This is the latest version, there is no problem with the firmware.  发自我的iPhone

…

------------------ Original ------------------ From: doenermann ***@***.***> Date: Mon,Nov 10,2025 9:07 PM To: Koenkk/zigbee2mqtt ***@***.***> Cc: jomders ***@***.***>, Mention ***@***.***> Subject: Re: [Koenkk/zigbee2mqtt] Coolo CS-201Z Soil Moisture Sensor(Discussion #27830) What about the older devices which stop reporting soil humidity after a couple hours/days completely? Will there be an update or are they wasted money and garbage now? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[jjsmackay]

I have four devices on 0122052017. If these can not be fixed, what is the process to RMA? Coolo will replace with working devices with working firmware?

[Nisbo]

@13717033460
What is the latest Firmware ? Is it 0126082025 ? My firmware is 0122052017. How can I upgrade the firmware ?

[llljjj7]

@13717033460
Hi
I purchased a soil sensor (modelId: ZG-303Z, vendor: HOBEIAN), but it seems to be linked to a different definition.
Since Zigbee2MQTT uses the zigbeeModel field for matching, it should be associated with the HOBEIAN definition, but it’s currently being matched to the COOLO vendor instead, which causes some functions not to work properly.
I don’t have any COOLO devices, so could you please check and correct this issue?

HOBEIAN definition

Coolo definition

[13717033460]

Hello, I tested it, ZG-303Z The corresponding DP function points are as follows:
[106, "dry", tuya.valueConverter.raw],
[5, "temperature", tuya.valueConverter.divideBy10],
[109, "humidity", tuya.valueConverter.raw],
[3, "soil_moisture", tuya.valueConverter.raw],
[15, "battery", tuya.valueConverter.raw],
[9, "temperature_unit", tuya.valueConverter.temperatureUnit],
[104, "temperature_calibration", tuya.valueConverter.localTempCalibration3],
[105, "humidity_calibration", tuya.valueConverter.localTempCalibration2],
[102, "soil_calibration", tuya.valueConverter.localTempCalibration2],
[111, "temperature_sampling", tuya.valueConverter.raw],
[112, "soil_sampling", tuya.valueConverter.raw],
[110, "soil_warning", tuya.valueConverter.raw],