ESPHome 2026.8 now supports configuring wifi: and ethernet: together, with automatic interface priority/failover via network: (#14255, #17797).
Could R_PRO-1_W.yaml and R_PRO-1_ETH.yaml therefore be consolidated into a single configuration, following current ESPHome best practices?
network:
priority:
- ethernet
- wifiThis would provide Ethernet first with automatic Wi-Fi fallback/failback, while reducing duplicated YAML, firmware variants, and maintenance.
Preliminary test
Tested successfully on an R-PRO-1 with ESPHome 2026.8.0. A minimal config adding the onboard W5500 alongside the existing Wi-Fi configuration compiles, boots, and initializes both interfaces correctly:
INFO ESPHome 2026.8.0
[C][ethernet]: Ethernet:
[C][ethernet]: Connected: NO
[C][ethernet]: Type: W5500
[C][wifi]: WiFi:
[C][wifi]: Connected: YES
[C][wifi]: IP Address: 192.168.1.133
Full Ethernet priority/failover/failback testing is still in progress.
For a consolidated configuration, may it would also make sense to eventually replace the separate wifi_info / ethernet_info IP sensors with a single active interface-aware network IP sensor. ESPHome 2026.8.0 already switches the route dynamically, but I'm not sure if this is possible. Maybe it is worth investigating?
ESPHome 2026.8 now supports configuring
wifi:andethernet:together, with automatic interface priority/failover vianetwork:(#14255, #17797).Could
R_PRO-1_W.yamlandR_PRO-1_ETH.yamltherefore be consolidated into a single configuration, following current ESPHome best practices?This would provide Ethernet first with automatic Wi-Fi fallback/failback, while reducing duplicated YAML, firmware variants, and maintenance.
Preliminary test
Tested successfully on an R-PRO-1 with ESPHome 2026.8.0. A minimal config adding the onboard W5500 alongside the existing Wi-Fi configuration compiles, boots, and initializes both interfaces correctly:
Full Ethernet priority/failover/failback testing is still in progress.
For a consolidated configuration, may it would also make sense to eventually replace the separate
wifi_info/ethernet_infoIP sensors with a single active interface-aware network IP sensor. ESPHome 2026.8.0 already switches the route dynamically, but I'm not sure if this is possible. Maybe it is worth investigating?