Closed slakichi closed 3 weeks ago
I started to create a PR and then I noticed that you had already shown the required change. Why don't you make a PR?
poll_period_ms
should be configurable (but I'm hassle with it)@slakichi, it's very simple to create a PR, you'll need to fork the repo, create a new branch from main, do the changes and commit them, then push the branch to GitHub, create a new Pull Request and choose your branch as the source.
I was just coming here to make the same change, @slakichi if you don't mind I am happy to open this PR?
Everyone seemed to want me to submit a PR, so I submitted a Draft, putting the document out of my mind. ... There seemed to be an error immediately.
There's no error, it's just waiting for review :) Thanks!
The problem
W5500 can build without interrupt_pin configuration, but actually, ESPHome firmware will setup W5500 ethernet driver with uninitialized interrupt pin config. This cause infinite crash at initialize ethernet component. Confirmed with M5Stack M5AtomS3 Lite with M5Stack ATOMIC PoE Base W5500
Which version of ESPHome has the issue?
2024.9.0
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
M5AtomS3 Lite
Component causing the issue
ethernet
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
This may cause by uninitialized
EthernetComponent::interrupt_pin_
(and not supported polling mode). Workaround Fix (polling interval is set sloppy and this causes the ESP32 core with high temperature(~75C), but it works)