Open raidnet-ms opened 1 year ago
Recovery: failed, SDA is held low on the bus
You didn't change anything?
Hi ssieb, sorry I posted the issue before completing all fields. now I edited it properly. I changed nothing, not the hardware, not the firmware. Esphome got the update automatically while yesterday I updated the firmware and suddenly I noticed sensors on i2c stopped working.
Actually, this looks like it might be a general gpio issue. We're investigating.
Let me know if you need any test. I'm going to check if i get this problem on other hardware.
with scan set to false I get only errors from both sensors:
[09:26:18][E][aht10:139]: Communication with AHT10 failed! [09:26:18][W][ccs811:166]: Communication failed! Is the sensor connected?
and no scan errors of course.
Could it be related to https://github.com/esphome/issues/issues/3909 (change of timing)?
No, that's specific to the Dallas. This appears to be a general problem with reading a gpio that switches state. i2c on 8266 is software.
Oh, you are right, sorry. https://github.com/esphome/esphome/commit/8fd93122545bfbc76a2e7df66a619191e66a5b10 is dallas specific, I remembered incorrectly.
I'm also having a similar issue with i2c to a ina219 on a RP2040 Pico W, this causes the board to not start:
i2c: sda: GPIO6 scl: GPIO7
I also can't say if it worked previously because this is the first time setting it up.
I have the same issue on Pi Pico W. When I configure I2C, the board will connect to wifi, but any communication with it is not possible (even over serial), and, of course, HA won't discover/connect to the Pico. The moment I disable I2C, these problems go away. The exact same config worked fine on 2022.03 with a D1 Mini.
Is the d1 working with 2022.12.3?
The D1 Mini's regulator died, so I can't test that. The idea was to slowly move to Picos all around the house since ESPs and regulators are a never-ending horror story. :-(
Same issue here, identical logs to raidnet-ms. Has there been any solution found??
Bumping this.
I do not have any issues on 8266 D1 Mini V4.0 devices, but all of my ESP32s (standard wroom, s2 wrover, s2 wroom) will:
With i2c scanning enabled:
With I2c scanning disabled:
Bumping too. Still the same issue on RPi Pico W, updating to the latest ESPHome release did not help.
The problem
After updating esphome and the firmware on a device using ccs811 and aht10 sensors, they are not working anymore.
In the logs I get errors from i2c
Which version of ESPHome has the issue?
2022.12.x
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2022.12.x
What platform are you using?
ESP8266
Board
d1mini
Component causing the issue
ccs811 and aht10
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
esphome 2022.11.x was working perfectly. I had some issues with aht10 on esphome 2022.10.x, but not related to i2c connection. The sensor was going timeout after few hours while with 2022.11 I had absolute no issues.