search

lubeda / EspHoMaTriXv2

A simple DIY status display with a 8x32 RGB LED matrix, implemented with esphome.io and Home Assistant.
MIT License
274 stars 25 forks source link

[BUG] infinite reboot #22

Closed lubeda closed 1 year ago

lubeda commented 1 year ago

Bug report

Describe the bug

Altleast since the introduction of bitmap_screen there are some unwanted reboots. Especially on a planed reboot the display stays in a boot loop.

There is no clear cause visible. Possible this is related to the network interface.

Additional information

To Reproduce

Steps to reproduce the behavior:

Expected behavior

A clear and concise description of what you expected to happen.

Configuration

(optional) The YAML you used in epshome without any password

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

(optional) Add relevant logs which could help tackle the problem.

Services calls

(optional) The YAML of your service calls
lubeda commented 1 year ago

I think this issue is related to https://github.com/esphome/issues/issues/1960

On ESP32 platforms there is a workaround by using PROGMEM but for ESP8266 with even fewer RAM I don't know yet

lubeda commented 1 year ago

@jblb Hi for ESP32 devices, you can try the develop branch ("it works on my system" :-)) For ESP8266 devices, I don't know yet.

trip5 commented 1 year ago

I have an old Awtrix that absolutely works using develop branch. Just flashed now. I had to remove a lot of the features (no buzzer, no TM chip) but it works.

Edit: I just realized I didn't say that it is driven by a D1 Mini Clone (ESP8266MOD)... I can even pull out the D1 and drop in another.

lubeda commented 1 year ago

I can't resolve this issue because the cause is not only my component. The ESP-platform is limited in resources, especially RAM. During runtime this can cause problems, depending on what configuration you use, memory intensive components, like web server and MQTT will increase the change of this infinite reboots. I did not find a way to probably debug this issue, but it is there. Since EspHoMaTriXv2 needs a lot of RAM too, you have to reduce the components and lambdas in your YAML.