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

Add wifi ip address #2144

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

openPhiL
Copy link

Hi there.
I am not able to communicate to the standard device_name.local logic in my setup, I have to give esphome the IP address that the device actually has. That is what the parameter use_address is for ( https://esphome.io/components/wifi.html#configuration-variables )

I have added that parameter and a default to your solution.

I have added a default to avoid warnings during compilation if none is defined. -> but I am unsure if that is the correct default. I tried nothing ( "" ), I tried "auto".. all those a problematic, so I think this device_name.local works.

Eventually, now it is possible to use this parameter like this in the yaml:

substitutions:

###### CHANGE ME START ######

  device_name: "egnspanel" 
  wifi_ssid: "IoT_wifi"
  wifi_password: "pizugipüghhüu"
  wifi_ipaddress: 172.16.21.29

  nextion_update_url: "http://10.0.1.2:8123/local/nspanel_eu.tft" # URL to local tft File
#  nextion_update_url: "https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/main/nspanel.tft" # URL to Github
##### CHANGE ME END #####

greetings,
PhiL

Details of the parameter in the esp home documentation: https://esphome.io/components/wifi.html
moved higher due to compiling error
so no warnings appear during compilation
@edwardtfn
Copy link
Collaborator

@illuzn
Copy link
Contributor

illuzn commented Jul 4, 2024

Discovery works via mDNS: https://esphome.io/components/mdns.html

It is highly likely that mDNS is incorrectly configured in your environment.

By the way, the .local TLD is a reserved TLD exclusively for mDNS. If you want to route using the ordinary IP/DNS system there isn't a reserved name for that as yet (although, the name .internal has been proposed to be used for this purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants