Open DEHTIRE opened 2 weeks ago
Yes, please do so.
Please install the current version from GitHub - it should support the sensor.
A.
I've installed 1.10.4 from Github. In advance I deleted my old exclusion of TS0601. I deleted the existing devices "Feucht Rosenbogen" and "Feucht "Garten". Then I paired them again. Log said "Interview successful".
After waiting >30 min, I got
and
So both temp are zero and only one moisture is more than zero !? How to proceed?
you need to verify which values are published by the device. the easiest method is to enter aabcef2;a7c0802
into the state zigbee.0.info.debugmessages
, then wait for a while and check the log for warn messages with the keyword "ELEVATED". There should be 2 messages for every value the sensor publishes to ioBroker.
A.
ELEVATED.docx Datapoints are still 0 / 0 and 0 / 29 No "ELEVATED"-logs of the first device (aabcef2).
Please post the log into the comment, not as a proprietary document (which I cannot open). If there is no entry for aabcef2, then the coordinator does not receive any data from the device. This can have any number of reasons. I would attempt to reconfigure the device from the device tile.
For the second device, if you read the text of the messages, you should be able to tell if the 0 values for the temperature are sent from the device or not.
A. p.s. you don't necessarily need to post duplicate messages, if there are too many messages in the log.
Ok, thanks. It seems that temperature was sent, but 0 is of course wrong (Germany, Berlin, summer ;-)) There is a third device of this type which works fine. What should I do in detail to delete the two "wrong" devices completely and re-pair them?
zigbee.0 2024-06-16 16:08:30.078 warn ELEVATED publishToState: value generated '"high"' from device a4c13815fa7c0802 for 'State of the battery'
zigbee.0 2024-06-16 16:08:30.078 warn ELEVATED publishToState: message received '{"battery_state":"high"}' from device a4c13815fa7c0802 type 'TS0601_soil'
zigbee.0 2024-06-16 16:08:30.076 warn ELEVATED publishToState: value generated '134' from device a4c13815fa7c0802 for 'Link quality'
zigbee.0 2024-06-16 16:08:30.076 warn ELEVATED publishToState: message received '{"linkquality":134}' from device a4c13815fa7c0802 type 'TS0601_soil'
zigbee.0 2024-06-16 16:08:29.964 warn ELEVATED publishToState: value generated '100' from device a4c13815fa7c0802 for 'Battery percent'
zigbee.0 2024-06-16 16:08:29.964 warn ELEVATED publishToState: message received '{"battery":100}' from device a4c13815fa7c0802 type 'TS0601_soil'
zigbee.0 2024-06-16 16:08:29.842 warn ELEVATED publishToState: value generated '29' from device a4c13815fa7c0802 for 'Measured soil moisture value'
zigbee.0 2024-06-16 16:08:29.842 warn ELEVATED publishToState: message received '{"soil_moisture":29}' from device a4c13815fa7c0802 type 'TS0601_soil'
zigbee.0 2024-06-16 16:08:29.756 warn ELEVATED publishToState: value generated '0' from device a4c13815fa7c0802 for 'Temperature'
zigbee.0 2024-06-16 16:08:29.755 warn ELEVATED publishToState: message received '{"temperature":0}' from device a4c13815fa7c0802 type 'TS0601_soil'
Mod-Edit: Code tags for logs.
Deleting and re-pairing the device will do nothing for the ..a7c0802 Device, as it actively reports 0 Degrees as temperature. This is no software issue. I would assume that you have a device with a broken temperature sensor. You can attempt to enter the value {"temperature_calibration" : 2}
into the send_payload and see if the reported temperature changes. Similarly, you can modify the precision for the temperature by sending {"temperature_precision":3}
For the ..aabcef2 device, it may make a difference to attempt to reconfigure the device using this button: (note - different device, I don't have any of those)
I'll check and try to delete. Thanks a lot for your effort.
Can you please add the following Tuya TS0601 sensor?
if that helps: https://www.zigbee2mqtt.io/devices/TS0601_soil.html