Klaus Riegler
Klaus Riegler
Oh, and installed Zigbee adapter 1.10.3 
Thank you for your quick response, Asgothian. I have now installed version 1.10.5 from Github, deleted the soil moisture sensor, restarted the host, and re-paired the sensor. Unfortunately, without success......
There's no rush. I'm happy to wait. **_;o)_**
This morning I installed the current version 10.5.0 from Github, deleted the sensor and restarted the host. Unfortunately, the soil moisture sensor is not recognized again. Everything is the same...
The sensor's object tree.  Text in "Value": `{"type":"attributeReport","data":{"65503":"�\u000f*.\u0019�\u000f*.\u0007\u0000\u0000\u0000\u0000\u0011"},"linkquality":127,"groupID":0,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":254,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}`
``` klaus@raspi4iobroker:/opt/iobroker $ npm list zigbee-herdsman-converters [email protected] /opt/iobroker └─┬ [email protected] (git+ssh://[email protected]/ioBroker/ioBroker.zigbee.git#b395620c3af1915587feec6fcad9f222d8531126) └── [email protected] ```
Sorry, I was away for a few days. Today I installed the latest version of Git. Unfortunately, without success. The sensor's response is: `{"type":"attributeReport","data":{"65503":"��B.\u0019��B.\u0007\u0000\u0000\u0000\u0000\u0011"},"linkquality":149,"groupID":0,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":249,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}`
>@Klarie2 Please verify that the device in question reports as _TZE284_sgabhwa6. This device is definitely supported in 1.10.5. In this case, you may have to remove the device and pair...
A device is created but the only data point is the link quality. See screenshot of the object tree. I can't look at the "tuya.ts" until after the weekend. ![Bildschirmfoto...
@asgothian > @Klarie2: Something does not add up here. The code for the device clearly lists the given manufacturer ID, so the device should be recognized (see this code) >...