01-15-2026, 06:16 AM
Hi Admin
Using ESPHome and Homeassistant, the publish_initial_state warning has been there for some time when compiling. Is this an option we fix in YAML or something the ESPHome people will sort with their code ?
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq/#why-am-i-...pping-pins
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
Many Thanks..Peter
Using ESPHome and Homeassistant, the publish_initial_state warning has been there for some time when compiling. Is this an option we fix in YAML or something the ESPHome people will sort with their code ?
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq/#why-am-i-...pping-pins
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
Many Thanks..Peter