SHT4X: Failed to reset the device.

[khc]

Describe the bug

if (!device_is_ready(sht)) {
printk("Device %s is not ready.\n", sht->name);
return 0;
}

I'm having trouble resetting my device.

Is there a way to fix this?

Relevant log output

[00:00:00.269,836] <err> SHT4X: Failed to reset the device.
*** Booting nRF Connect SDK v3.1.0-6c6e5b32496e ***
*** Using Zephyr OS v4.1.99-1612683d4010 ***
SHT4X: 26.20 Temp. [C] ; 15.17 RH [%]
SHT4X: 26.23 Temp. [C] ; 15.16 RH [%]
SHT4X: 26.20 Temp. [C] ; 15.15 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.15 RH [%]
SHT4X: 26.22 Temp. [C] ; 15.13 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.16 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.16 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.14 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.04 RH [%]
SHT4X: 26.23 Temp. [C] ; 15.10 RH [%]
SHT4X: 26.22 Temp. [C] ; 15.11 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.10 RH [%]
SHT4X: 26.21 Temp. [C] ; 15.09 RH [%]

Environment

os - windows

toolchain - v3.1.0

[Vidar Berg]

Hello,

The error is logged in the driver init here: https://github.com/nrfconnect/sdk-zephyr/blob/c09c6abd11695d6b9c2ea24c4e88822eee9ff3f9/drivers/sensor/sensirion/sht4x/sht4x.c#L191. I assume the sensor might simply not have been ready to receive the command this early on startup and therefore NACKed it since the log shows that the measurement commands sent afterwards work just fine. To confirm this theory you could try adding a delay before the reset command. E.g.,

    /* Extra delay */
    k_sleep(K_MSEC(SHT4X_RESET_WAIT_MS));

	rc = sht4x_write_command(dev, SHT4X_CMD_RESET);
	if (rc < 0) {
		LOG_ERR("Failed to reset the device.");
		return rc;
	}

Best regards,

Vidar