Yesterday, 06:04 PM
I found a reproducible problem with an SHT30/SHT31 sensor on KC868-A16v3 running KCS v3.27.2.
Hardware:
After a complete 12 V power cycle, the SHT30 works immediately and temperature/humidity values are displayed normally.
However, if I use Reboot from the KCS web interface, the sensor stops working.
The application log then shows:
KCS retries the sensor, but it may remain unavailable.
How to reproduce:
Initially one sensor had an extended cable, so I suspected the I2C cable length. I then tested a second SHT30 with its original unmodified cable, and it failed immediately after the first KCS software reboot in exactly the same way.
Therefore the cable extension is not the cause.
A complete power cycle of the A16v3/sensor consistently restores operation, while a KCS software reboot can cause the sensor to fail.
It looks like the SHT30/I2C bus or sensor is not being correctly reset/reinitialized after an ESP32 software reboot.
Could you please reproduce this with an A16v3 + SHT30 and check the sensor/I2C initialization after software reboot?
Hardware:
- KC868-A16v3
- KCS v3.27.2
- KinCony SHT30 temperature/humidity sensor
- I2C address 68 decimal (0x44)
After a complete 12 V power cycle, the SHT30 works immediately and temperature/humidity values are displayed normally.
However, if I use Reboot from the KCS web interface, the sensor stops working.
The application log then shows:
Code:
i2c.master: I2C transaction unexpected nack detected
i2c.master: s_i2c_synchronous_transaction(872): I2C transaction failed
i2c.master: i2c_master_transmit(1074): I2C transaction failed
sensor: sht31 error, id=0How to reproduce:
- Power off the whole A16v3 (12 V supply).
- Power it on again.
- SHT30 data appears immediately and works normally.
- In the KCS web interface select Reboot.
- After the reboot the SHT30 is no longer available and the log reports I2C NACK / sht31 error.
- Remove 12 V power completely and power the A16v3 again.
- SHT30 works immediately again.
Initially one sensor had an extended cable, so I suspected the I2C cable length. I then tested a second SHT30 with its original unmodified cable, and it failed immediately after the first KCS software reboot in exactly the same way.
Therefore the cable extension is not the cause.
A complete power cycle of the A16v3/sensor consistently restores operation, while a KCS software reboot can cause the sensor to fail.
It looks like the SHT30/I2C bus or sensor is not being correctly reset/reinitialized after an ESP32 software reboot.
Could you please reproduce this with an A16v3 + SHT30 and check the sensor/I2C initialization after software reboot?

