Closed wwebers closed 3 years ago
I found the cause of the problem:
The display used the I2C protokoll. Maximum rate for the Wemos D1 seem to bee 100khz, which seem to be too slow to keep the default display refresh rate at 5s! As a result, it looks like this breaks the hard requirement of the ESPHome "scheduler" to not spend more than 10ms. In the end, the other components don't get a chance to handle their loops.
Solution:
Increase the update_interval to e.g. 10s.
- platform: ssd1327_i2c
model: "SSD1327 128x128"
update_interval: 10s
id: clock_display
address: 0x3D
lambda: |-
it.strftime( 0, 0, id(my_font), "%Y-%m-%d %H:%M:%S", id(sntp_time).now());
Alternatively, one could try to connect the display to the SPI-bus.
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Windows 10, python 3.9, pip
ESP (ESP32/ESP8266, Board/Sonoff):
ESP8266, Wemos D1 mini
ESPHome version (latest production, beta, dev branch)
1.16.2
Affected component:
WiFi: https://esphome.io/components/wifi.html SSD1327_I2C: https://esphome.io/components/display/ssd1327.html
Description of problem: With the display component enabled the Wemos D1 is unable to connect to my WiFi AP. Its cannot even create the fallback AP.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried: As soon as I disable the display component everything works fine. Including other I2C devices,