Replies: 1 comment 1 reply
-
It is better to create an issue for this instead of a discussion topic. I have no experience with setting a static IP myself. If you make changes to the YAML config via ESPHome dashboard and install the firmware. Then it could very well be that a firmware update from the repository will undo your changes. ./Klaas |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a problem assigning a static IP address to glow. If I assign a static IP address as described in the ESPhome WiFi component documentation, I get an error message during installation stating that the manifest could not be reached due to a DNS failure.
relevant yaml-section
Below is the relevant installation log portion.
Apparently, no DNS server is assigned due to which the address for the manifest site cannot be resolved. In this case, I do not get the notification that version 4.2.3 is available in HA. The static IP address assigned works.
If I add a DNS server to the manual IP definition, e.g. DNS1: 1.1.1.1, then the manifest is accessed and after installation, I get the notification of a firmware update to 4.2.3.The static address initially assigned still works.
After performing the update to 4.2.3, the static IP initially defined is disregarded and a different IP address is assigned through DHCP.
Am I misunderstanding how to define the static IP, or is there something else I am not aware of?
Beta Was this translation helpful? Give feedback.
All reactions