mirror of
https://github.com/esphome/esphome.git
synced 2026-07-10 17:05:36 +00:00
kbx81
eb64707d94
PR #14255 sets NETWORK_PRIORITY_BASE = 300.0, but PR #14012's NetworkComponent uses setup_priority::AFTER_BLUETOOTH = 300.0f. When the highest-priority interface (first in the priority list) tied with NetworkComponent at 300, the runtime tie-break was determined by registration order — and NetworkComponent registers AFTER ethernet (its codegen runs at CoroPriority.NETWORK_SERVICES = 55, below COMMUNICATION = 60 used by ethernet/wifi). Result: ethernet's setup() ran before NetworkComponent::setup(), esp_netif_init() had not yet been called, esp_netif_new() returned NULL, and EthernetComponent::setup() dereferenced NULL in esp_netif_attach() — LoadProhibited crash at boot. Drop the base to 250.0 (matches the historical setup_priority::WIFI / ::ETHERNET default, so a single-entry priority list behaves identically to a no-priority-block config) and shrink the step to 5.0 to keep all interfaces in the same priority band, above BEFORE_CONNECTION (220.0) and below AFTER_BLUETOOTH (300.0).
