[New device support]: Tuya Soil Sensor _TZE200_myd45weu

[kris969]

Link

https://fr.aliexpress.com/item/1005004705106578.html?spm=a2g0o.order_list.0.0.6e935e5bqgigNf&gatewayAdapt=glo2fra

Database entry

{"id":29,"type":"EndDevice","ieeeAddr":"0xa4c138bcc914bc7f","nwkAddr":34574,"manufId":4417,"manufName":"_TZE200_myd45weu","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[4,5,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"'�\u0014+i(�\u0014+i+�\u0014+i,�\u0014+i;�\u0014+i<�\u0014+i��\u0014+f��\u0014+\u0012","65506":56,"65508":0,"stackVersion":0,"dateCode":"","appVersion":72}}},"binds":[{"cluster":0,"type":"endpoint","deviceIeeeAddress":"0x00212effff071444","endpointID":1}],"configuredReportings":[],"meta":{}}},"appVersion":72,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{"configured":821693351},"lastSeen":1669455534902,"defaultSendRequestWhen":"immediate"}

Comments

Hi, I have just receive this Tuya Soil Sensor that seems to be new on the market. I tried to pair it using the dev branch, but it is not recognized yet.

Although I was coding in the past, I'm not comfortable with js. I begun writing an external converter but I thing it will be more efficient if someone else will do this job.

I give you my first work on converter, even job is'nt finished.

I give you here after the debug log I got:

2022-11-26 10:07:20Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":57856}' from endpoint 1 with groupID null

2022-11-26 10:07:21Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[2],"type":"Buffer"},"datatype":4,"dp":14}],"seq":58112}' from endpoint 1 with groupID null

many thanks for all ;)

External converter

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require("zigbee-herdsman-converters/lib/tuya");

const definition = {
    // Since a lot of Tuya devices use the same modelID, but use different data points
    // it's usually necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE200_myd45weu'
        },
    ],
    model: 'QT-07S',
    vendor: 'Unknown',
    description: 'Soil Sensor',
    fromZigbee: [
        fz.ignore_basic_report, // Add this if you are getting no converter for 'genBasic'
        fz.tuya_data_point_dump, // This is a debug converter, it will be described in the next part
    ],
    toZigbee: [
        tz.tuya_data_point_test, // Another debug converter
    ],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: async (device, coordinatorEndpoint, logger) => {
        const endpoint = device.getEndpoint(1);
        await reporting.bind(endpoint, coordinatorEndpoint, ['genBasic']);
    },
    // Here you should put all functionality that your device exposes
    exposes: [],

};

module.exports = definition;

Supported color modes

No response

Color temperature range

No response

[kris969]

Here after an extract of the relative tuya dump file:

1669453325405 0xa4c138bcc914bc7f c800 00 0f 02 00 00 00 64 1669453325614 0xa4c138bcc914bc7f c900 00 0e 04 02 1669453346768 0xa4c138bcc914bc7f ca00 00 0f 02 00 00 00 64 1669453346988 0xa4c138bcc914bc7f cb00 00 0e 04 02 1669453368112 0xa4c138bcc914bc7f cc00 00 0f 02 00 00 00 64 1669453368338 0xa4c138bcc914bc7f cd00 00 0e 04 02

[Koenkk]

I suggest to start with the following converter and then adding the datapoints to tuyaDatapoints. The hardest part is figuring out what the datapoints mean, usually this is done via the TuYa gatway: https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const e = exposes.presets;
const ea = exposes.access;

const definition =     {
    fingerprint: tuya.fingerprint('TS0601', ['_TZE200_myd45weu']),
    model: 'TS0601_soil',
    vendor: 'TuYa',
    description: 'Soil sensor',
    fromZigbee: [tuya.fzDataPoints],
    toZigbee: [tuya.tzDataPoints],
    configure: tuya.configureMagicPacket,
    exposes: [],
    meta: {
        multiEndpoint: true,
        tuyaDatapoints: [
            [14, 'dp_14', tuya.valueConverter.raw],
            [15, 'dp_15', tuya.valueConverter.raw],
        ],
    },
    whiteLabel: [
        {vendor: 'Yieryi', model: 'THE01840'},
    ],
};

module.exports = definition;

[kris969]

Many thanks for your reply in such a short time!

On my side I am available to continue on this topic, and to be as useful as possible, even if ti's a new domain for me ;(

Using your template converter, it gives the following return, in the zigbee2mqtt state screen: "dp_14": 2, "dp_15": 100, that is, of course, conform to tuya dump log

My assumption is that "100" must be battery level, cause the batteries I'm using are new.

I don't know what's value "2" is relative to. This sensor is supposed to report temperature, humidity an battery levels, but only values OxOE (dp_14) and OxOF (dp_15) are present in the dump log. I suppose the value "2" must be relative to humidity, a relative low value indeed. Actually it's rainy outside and the soil is very wet. I don't understand why there is no data relative to temperature.

I tried to map these data in the expose section : exposes: [e.humidity(), e.battery() ]. It's evident that something is missing and that my knowledge need to be improved.

I will spend time on https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html to identify more information about this sensor.

at least but not last, could you give me your understanding about this extract from dump log : 1669454228416 0xa4c138bcc914bc7f 1000 00 0f 02 00 00 00 64 1669454228620 0xa4c138bcc914bc7f 1100 00 0e 04 02 1669454269599 0xa4c138bcc914bc7f 1200 00 0f 02 00 00 00 64 1669454269835 0xa4c138bcc914bc7f 1300 00 0e 04 02 1669454290986 0xa4c138bcc914bc7f 1400 00 0f 02 00 00 00 64 1669454291126 0xa4c138bcc914bc7f 1500 00 0e 04 02 1669454332351 0xa4c138bcc914bc7f 1600 00 0f 02 00 00 00 64 1669454332510 0xa4c138bcc914bc7f 1700 00 0e 04 02 1669454373686 0xa4c138bcc914bc7f 1800 00 0f 02 00 00 00 64 1669454373893 0xa4c138bcc914bc7f 1900 00 0e 04 02

[Koenkk]

The exposes part will come later, we first need to figure out the data points.

Are there any more datapoints send by the device? You can check this by activating the debug log, you should see Datapoint XX not defined for..

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging.

[kris969]

My debug level is already activated ;)

Other datapoints seems not to be sent by the device. so far, I haven't seen "Datapoint XX not defined for"

Here is an extract of log.txt | grep myfriendlyname:

Zigbee2MQTT:info 2022-11-28 19:42:18: GARDEN_SOIL_01 (0xa4c138bcc914bc7f): TS0601_soil - TuYa Soil sensor (EndDevice) Zigbee2MQTT:debug 2022-11-28 19:42:18: Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":62464}' from endpoint 1 with groupID null Zigbee2MQTT:debug 2022-11-28 19:42:18: Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":62464}' from endpoint 1 with groupID null Zigbee2MQTT:debug 2022-11-28 19:42:18: Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":62464}' from endpoint 1 with groupID null Zigbee2MQTT:debug 2022-11-28 19:42:19: Passive device 'GARDEN_SOIL_01' was last seen '0.00' hours ago. Zigbee2MQTT:info 2022-11-28 19:42:19: MQTT publish: topic 'zigbee2mqtt/GARDEN_SOIL_01/availability', payload 'online' Zigbee2MQTT:info 2022-11-28 19:42:19: MQTT publish: topic 'zigbee2mqtt/GARDEN_SOIL_01', payload '{"device":{"applicationVersion":72,"dateCode":"","friendlyName":"GARDEN_SOIL_01","hardwareVersion":1,"ieeeAddr":"0xa4c138bcc914bc7f","manufacturerID":4417,"manufacturerName":"_TZE200_myd45weu","model":"TS0601_soil","networkAddress":34574,"powerSource":"Battery","stackVersion":0,"type":"EndDevice","zclVersion":3},"dp_14":2,"dp_15":100,"last_seen":"2022-11-28T19:42:18.776Z","linkquality":244}' Zigbee2MQTT:debug 2022-11-28 19:42:25: Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,100],"type":"Buffer"},"datatype":2,"dp":15}],"seq":63488}' from endpoint 1 with groupID null Zigbee2MQTT:info 2022-11-28 19:42:25: MQTT publish: topic 'zigbee2mqtt/GARDEN_SOIL_01', payload '{"device":{"applicationVersion":72,"dateCode":"","friendlyName":"GARDEN_SOIL_01","hardwareVersion":1,"ieeeAddr":"0xa4c138bcc914bc7f","manufacturerID":4417,"manufacturerName":"_TZE200_myd45weu","model":"TS0601_soil","networkAddress":34574,"powerSource":"Battery","stackVersion":0,"type":"EndDevice","zclVersion":3},"dp_14":2,"dp_15":100,"last_seen":"2022-11-28T19:42:25.085Z","linkquality":220}' Zigbee2MQTT:debug 2022-11-28 19:42:25: Received Zigbee message from 'GARDEN_SOIL_01', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[2],"type":"Buffer"},"datatype":4,"dp":14}],"seq":63744}' from endpoint 1 with groupID null Zigbee2MQTT:info 2022-11-28 19:42:25: MQTT publish: topic 'zigbee2mqtt/GARDEN_SOIL_01', payload '{"device":{"applicationVersion":72,"dateCode":"","friendlyName":"GARDEN_SOIL_01","hardwareVersion":1,"ieeeAddr":"0xa4c138bcc914bc7f","manufacturerID":4417,"manufacturerName":"_TZE200_myd45weu","model":"TS0601_soil","networkAddress":34574,"powerSource":"Battery","stackVersion":0,"type":"EndDevice","zclVersion":3},"dp_14":2,"dp_15":100,"last_seen":"2022-11-28T19:42:25.318Z","linkquality":220}'

[kris969]

here are technical specifications, available on: https://www.aliexpress.com/item/1005004705106578.html?spm=a2g0o.order_list.0.0.21ef5e5bfgxp4o&gatewayAdapt=glo2fra

Specifications: Moisture measurement range: 0~100% Moisture accuracy: 0~50% (±3%) , 50~100% X(±5%) Temperature measurement range: -20°C~60°C Temperature accuracy: 1°C Communication protocol: Zigbee APP response time: 60s Power supply: 2 pcs AA dry batteries Size: 120*180*46.5mm Probe Length: 60mm Protection class: IP67

[kris969]

For your information, I tried to connect this device to a Tuya hub (G2H camera) with no success. I didn't find this device in Tuya sensors database. The initial idea was to check if a new firmware is available for update.

[Koenkk]

Without the datapoints there is little I can do here. Maybe you can try with the white rectangular TuYa hub.

[kris969]

My hub was not the correct one! I purchase a new one, it takes a couple of days to have it. I follow your guide to identify datapoint IDs, and that's it :

humidity : 3 Current temperature : 4 Temp unit convert : 9 --> remark : I don't see what it could be relative to??? Battery level state : 14 Battery level : 15

[Koenkk]

Please check with https://gist.github.com/Koenkk/868e23ad38c12fd14bed4fb83484b40e , I'm not sure about the battery_state, what appears in the z2m frontend -> device -> state?

[kris969]

here is the data reported in the z2m state tab :

{ "battery": 90, "battery_state": 2, "humidity": 40, "last_seen": "2022-12-02T17:43:31.892Z", "linkquality": 244, "temperature_unit": "celsius", "device": { "applicationVersion": 72, "dateCode": "", "friendlyName": "GARDEN_SOIL_01", "hardwareVersion": 1, "ieeeAddr": "0xa4c138bcc914bc7f", "manufacturerID": 4417, "manufacturerName": "_TZE200_myd45weu", "model": "TS0601_soil", "networkAddress": 23478, "powerSource": "Battery", "stackVersion": 0, "type": "EndDevice", "zclVersion": 3 } }

battery and humidity values are equivalent the ones previously reported when using Tuya app. battery state seems strange, as you anticipate. It seems there is no temperature value yet.

I stay in line...

[kris969]

Because no temperature as been reported, I looked closer to understand why it was not working. I found I have introduce a mistake in the temperature datapoint IDs I provided to you. Sorry for this waste of time ;(

So here is the right template: humidity : 3 Current temperature : 5 Temp unit convert : 9 --> remark : I don't see what it could be relative to??? Battery level state : 14 Battery level : 15

after correction, the state becomes: { "battery": 90, "battery_state": 2, "humidity": 41, "last_seen": "2022-12-02T20:13:20.551Z", "linkquality": 224, "temperature_unit": "celsius", "device": { "applicationVersion": 72, "dateCode": "", "friendlyName": "GARDEN_SOIL_01", "hardwareVersion": 1, "ieeeAddr": "0xa4c138bcc914bc7f", "manufacturerID": 4417, "manufacturerName": "_TZE200_myd45weu", "model": "TS0601_soil", "networkAddress": 23478, "powerSource": "Battery", "stackVersion": 0, "type": "EndDevice", "zclVersion": 3 }, "temperature": 11 }

my question is: why the temperature appears at the end, after the device block? I still have an misunderstanding that's why temperature value is 11? Of course it's not a z2m issue cause I got exactly the same value with Tuya application. I will have a look later to check if this value is changing over the time.

[kris969]

It is clearly explained: "Wireless soil temperature and humidity measuring instrument, which can measure soil humidity and temperature at the same time, and connect to Tuya APP through Zigbee."

It is confirm the humidity AND the temperature values are the ones from the soil. The temperature accuracy is 1°C, that's enough. During the last night the external temperature drop from 6°C to 3°C in free air. During this time the soil sensor goes from 11°C to 10°C. That's normal, cause soil temperature move slowly due to inertia.

I will in the next days do some more tests with different batteries levels to confirm how the battery_state changes.

That's all ;)

[Koenkk]

Great, note that we can also leave out the battery_state since we already have the battery (%)

[kris969]

I have done it, this morning. It was not so long ;) I got 2 values for battery_state: when battery_level is reported as 90% or 100% --> battery_state is 2 when battery_level is reported as 10% or lower --> battery_sate is 0

I wanted to use my supply lab to easily change the voltage and find the intermediate threshold, it was not a good idea! Due to a wrong action I killed the sensor ;(

I open the sensor, and I saw it's really well done. As supposed, there is a very little Negative Temperature Coefficient (NTC) resistance that is placed in the metallic lower part of the sensor to measure soil temperature.

The damage is around a MOSFET transistor and 2 resistors in the neighborhood. The MOSFET is easy to replace cause reference is writing on, but it's not the case concerning resistor. I's know impossible to get the values! I bought a new sensor. When I will receive it, I will be able to measure resistors values and to fix the damaged sensor. So I will not be able to continue with you until I will have received the new one.

Yes, I think you can publish it. Concerning battery_state maybe you can start with something like: {2: 'battery_full', 1: 'battery_medium', 0: 'battery_low', 4}

In a couple of days I will be able to continue to validate battery_sate and I will come back to you.

[denveronly]

looking for this topic have the same sensor with no support

[Koenkk]

I added the device!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[kris969]

Great!

I will test it as soon as possible...

Le dim. 4 déc. 2022, 19:30, Koen Kanters @.***> a écrit :

I added the device!

Changes will be available in the dev branch in a few hours from now. ( https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/15191#issuecomment-1336485736, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZSP4HXCWY5UJL2V4QKBY3WLTPLHANCNFSM6AAAAAASL5NQ44 . You are receiving this because you authored the thread.Message ID: @.***>

[cloudbr34k84]

When will this be available in Z2M as i bought and its not supported??

[cloudbr34k84]

looking for this topic have the same sensor with no support

same

[kris969]

Hi, I'm back ;)

It takes a long time to have the new device... I have received it this morning, paired it to a Tuya hub, just to check if firmware was ok: it was the case. Then I paired it to z2m For battery and humidity values it's ok. Unfortunately the temperature is not reporting in the z2m state frame even in the log. the value displayed is still zero.

Here after an example: Zigbee2MQTT:info 2022-12-24 11:13:34: MQTT publish: topic 'zigbee2mqtt/GARDEN_SOIL_01', payload '{"battery":100,"battery_state":"high","device":{"applicationVersion":72,"dateCode":"","friendlyName":"GARDEN_SOIL_01","hardwareVersion":1,"ieeeAddr":"0xa4c13805901f6d3e","manufacturerID":4417,"manufacturerName":"_TZE200_myd45weu","model":"TS0601_soil","networkAddress":30848,"powerSource":"Battery","stackVersion":0,"type":"EndDevice","zclVersion":3},"humidity":39,"last_seen":"2022-12-24T11:13:34.598Z","linkquality":255,"temperature_unit":"celsius"}'

The device picture is not available yet, but this must be normal, of course isn't totally complete at this step of integration. I will be available for more investigations as needed.

[kris969]

@cloudbr34k84

You need to use the dev branch, in docker-compose: image: koenkk/zigbee2mqtt:latest-dev

you will found this sensor is supported, its integration in z2m is on going.

[kris969]

@Koenkk

I have found where the issue is coming from.

with z2m version: 1.28.4-dev commit: [6d08a2f]

in file : zigbee-herdsman-converters/devices/tuya.js

we have:

{                                                                 
        fingerprint: tuya.fingerprint('TS0601', ['_TZE200_myd45weu']),
        model: 'TS0601_soil',                       
        vendor: 'TuYa',                                 
        description: 'Soil sensor',                                   
        fromZigbee: [tuya.fz.datapoints],                                                                                  
        toZigbee: [tuya.tz.datapoints],                                                                                    
        configure: tuya.configureMagicPacket,                                                                              
        exposes: [e.temperature(), e.humidity(), tuya.exposes.temperatureUnit(), e.battery(), tuya.exposes.batteryState()],
        meta: {                                                       
            tuyaDatapoints: [                                                
                [3, 'humidity', tuya.valueConverter.raw],                                                                  
                [4, 'temperature', tuya.valueConverter.divideBy10],          
                [9, 'temperature_unit', tuya.valueConverter.temperatureUnit],
                [14, 'battery_state', tuya.valueConverter.batteryState],
                [15, 'battery', tuya.valueConverter.raw],          
            ],                                                                                                             
        },                                                                                                                 
    },           

the line relative to temperature must be changed to: [5, 'temperature', tuya.valueConverter.divideBy10],

After having removed my device from z2m and pairing it again, it works !!! But the value must not be divided by 10. I tried to fix it using uya.valueConverter.raw but without success! I let you do this job, I'm not aware of how to do this...

So let me know when you will have time to integrate this last change in the dev branch, I will do a last check.

[cloudbr34k84]

@cloudbr34k84

You need to use the dev branch, in docker-compose: image: koenkk/zigbee2mqtt:latest-dev

you will found this sensor is supported, its integration in z2m is on going.

ill just wait for the non dev update to come though.

[Koenkk]

Great, assumed this can be closed now!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[kris969]

Hi,

A last change about temperature that don't need to be devided. I send a pull request around this, expecting I have done as it shoud? let me know.

I made testing this morning: it's ok!

regards ;)

Le dimanche 25 décembre 2022 à 08:04 -0800, Koen Kanters a écrit :

Great, assumed this can be closed now! Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[brianegge]

Thanks for the change! I purchased the same soil sensors, and they worked fine after I updated my setup.

[fliespl]

I just bought one of these and seeing strange thing about temperature. It reports 27 outside while its really 19. Added negative calibration of 8 and it went down to 11 on next report.

Also precision doesn't seem to work on my end. Only get full degrees.

Currently on edge since it adds support for my model.

[kris969]

The temperature reported is the soil one, don't compare it with the air one. It takes a lot of time, after putting it in the soil, to be stabilized. The temperature precision is given to be around 1°C. Let's say it can only be use to get an approximate soil temperature.  I have 2 of them since 6 month, it gives useful results to manage watering. 

Le mercredi 28 juin 2023 à 15:47 -0700, fliespl a écrit :

I just bought one of these and seeing strange thing about temperature. It reports 27 outside while its really 19. Added negative calibration of 8 and it went down to 11 on next report. Also precision doesn't seem to work on my end. Only get full degrees. Currently on edge since it adds support for my model. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[fliespl]

@kris969 thanks for explaining! That makes sense. Btw. Do you mind sharing thresholds used for irrigation?

[kris969]

About thresholds, I am not sure to have the right tune, cause there is a lake of rain where I am living and I need more feedback.

I can give you in the attach file the graph representing moisture in green and rain drops in yellow. Based on this, and considering soil aspect, I stop irrigation when moisture is above 40%, it's my baseline for now. 

My moisture sensor is placed in the garden out of the scope of irrigation. So I only consider water coming from rain. I am not saying it must be done like this, just telling you how I used it until now. Not sure I will not change this in the future.

We also have to consider the plants you have in your garden, some of them needs more or less water to be healthy. so we could consider different thresholds for different irrigation zones. 

So just to say there is not an unique solution, and we need time to understand.

Finally, don't forget, the best way to do it is the one you prefer ;)

Enjoy!

Le jeudi 29 juin 2023 à 10:28 -0700, fliespl a écrit :

@kris969 thanks for explaining! That makes sense. Btw. Do you mind sharing thresholds used for irrigation? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>