Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Static IP address disappears after firmware update #637

Open
mrclmller opened this issue Oct 28, 2024 Discussed in #636 · 1 comment
Open

Static IP address disappears after firmware update #637

mrclmller opened this issue Oct 28, 2024 Discussed in #636 · 1 comment
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@mrclmller
Copy link

Discussed in #636

Originally posted by mrclmller October 28, 2024
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

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Set up a wifi access point
  ap:
    ssid: '${friendly_name}'

  manual_ip:
    static_ip: 192.168.0.123
    gateway: 192.168.0.1
    subnet: 255.255.255.0

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.

[12:58:21][C][wifi:428]:   Local MAC: XX:B6:1F:28:XX:XX
[12:58:21][C][wifi:433]:   SSID: [redacted]
[12:58:21][C][wifi:436]:   IP Address: 192.168.0.123
[12:58:21][C][wifi:440]:   BSSID: [redacted]
[12:58:21][C][wifi:441]:   Hostname: 'home-assistant-glow-28702c'
[12:58:21][C][wifi:443]:   Signal strength: -23 dB ▂▄▆█
[12:58:21][C][wifi:447]:   Channel: 9
[12:58:21][C][wifi:448]:   Subnet: 255.255.255.0
[12:58:21][C][wifi:449]:   Gateway: 192.168.0.1
[12:58:21][C][wifi:450]:   DNS1: 0.0.0.0
[12:58:21][C][wifi:451]:   DNS2: 0.0.0.0
[12:58:21][D][wifi:626]: Disabling AP...
[12:58:21][C][web_server:100]: Setting up web server...
[12:58:21][C][api:026]: Setting up Home Assistant API server...
[12:58:21][I][app:062]: setup() finished successfully!
[12:58:21][  8018][E][WiFiGeneric.cpp:1438] hostByName(): DNS Failed for glow-energy.io
[12:58:21][  8020][E][WiFiClientSecure.cpp:135] connect(): start_ssl_client: -1
[12:58:21][W][http_request.arduino:110]: HTTP Request failed; URL: https://glow-energy.io/home-assistant-glow/manifest.json; Error: connection refused
[12:58:21][E][component:164]: Component http_request set Error flag: unspecified
[12:58:21][E][component:164]: Component http_request.update set Error flag: Failed to fetch manifest from https://glow-energy.io/home-assistant-glow/manifest.json

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?

It could be that something gets overwritten with the firmware update as Klaas mentions, however, I have no idea where to look further.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

1 participant