Open xuxiaohe0308 opened 2 years ago
Just reproduced this exact problem. Did you have a chance to test if it's i2c pin-dependent?
I have the same issue with TSL2591.
It does not seem to be pin related.
Checked with:
i2c:
sda: 16
scl: 17
If I remove either SDA or SCL connection to TSL2591 the device boots fine with:
[19:06:22][C][i2c.arduino:038]: I2C Bus:
[19:06:22][C][i2c.arduino:039]: SDA Pin: GPIO16
[19:06:22][C][i2c.arduino:040]: SCL Pin: GPIO17
[19:06:22][C][i2c.arduino:041]: Frequency: 50000 Hz
[19:06:22][C][i2c.arduino:044]: Recovery: bus successfully recovered
If TSL2591 is fully connected the device crashes here:
[19:05:40][I][i2c.arduino:161]: Performing I2C bus recovery
[19:05:45]E (10230) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
My controller is a "Goouuu-ESP32" (ESP-WROOM-32, nodemcu-32). Power via USB does suffice, right? Just checking every assumption.
I also tried to connect a CCS811 and another (unsupported) I2C device. Both worked fine.
I had similar issue and resolved it by checking sensor address and wiring. I tried to use power supply from GPIO pins but it looks like esphome initializes them after I2C and if anything is wrong with I2C it enters in reboot loop.
Thanks for everyone. I solved this problem by using shorter wires, so maybe this is a wire quality problem. But it's weird that I use the same wires on i2c on RaspberryPi and it works normally.
Thank you! I’ve traced the problem to a faulty SCD30 sensor. Replacing the sensor fixed the problem. We might want to document this somewhere.
On Aug 20, 2022, at 7:05 AM, Dmitry Polukhin @.***> wrote:
I had similar issue and resolved it by checking sensor address and wiring. I tried to use power supply from GPIO pins but it looks like esphome initializes them after I2C and if anything is wrong with I2C it enters in reboot loop.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
Hi I am using ESP32 (nodemcu-32s) and TSL2561 through i2c, and trying to use MQTT to publish sensor data. When I flash my ESP32 it seems to be stuck in some kind of dead loop (which is shown in the log below). Some important messages are like
Performing I2C bus recovery [21:31:02]E (10192) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
I think it is i2c's problem because when I delete i2c and TSL2561 configuration in the yaml file it can boot correctly. Also I try another BME280 sensor and the problem still exists. Can you solve my problem?Which version of ESPHome has the issue?
2022.3.2
What type of installation are you using?
pip
Which version of Home Assistant has the issue?
No response
What platform are you using?
ESP32
Board
nodemcu-32s
Component causing the issue
i2c
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response