Resolving IP address of esp32_02.local

ESPHome
21

Ah…so the IP address works, but there is something wrong with your API password.
You have to specify your API password in esp yaml:

# Enable Home Assistant API
api:
  password: !secret api_password

(which I specified in my secrets.yaml)

If you changed the password, you might want to remove the ESP home device from HA, so it will be re-added (and it will prompt for the new API password)

22

when I using the IP address of Simmelezer which is 192.168.1.33, in logs is the wrong password, but this IP address is the Simmelezer in the network and does not exist password.
When I tryed with ssid name and password in the yaml file it say, Resolving IP address of elkontrol1.local.
Im confused.

23

Passwd of API … maybe 214 or “ota” passwwd

24

try removing the esphome device from HA,
then when re-adding it will ask for the API password again.

(if you never added it before, just try to add it in ha, just open integrations/esphome and continue from there :wink:)

25

HI again,
has removed ESPHome from HA and has started again. But it will be the same mistake.
Do you know what the steps are for installing Slimmelezer +. How can factory reset Slimmelezer + to start the installation again?

  name: vattenfall

esp8266:
  board: esp01_1m

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "1cb288f7a3b7c9b2262c767536a301"

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Vattenfall Fallback Hotspot"
    password: "N1FIk1wTixN"

captive_portal: ``` 

INFO Successfully compiled program.
INFO Resolving IP address of vattenfall.local
ERROR Error resolving IP address of vattenfall.local. Is it connected to WiFi?
ERROR (If this error persists, please set a static IP address: https://esphome.io/components/wifi.html#manual-ips)
ERROR Error resolving IP address: Error resolving address with mDNS: Did not respond. Maybe the device is offline., [Errno -5] No address associated with hostname
26

now check your router to see which ipnumber your device “vattenfall.local” got

ADD: is this error from HA logfile ?

@chris4

27

here it worked, just have to finalize it from esphome in ha

28

I tryed to update manually with bin ( ._slimmelezer-2022.1.2.bin )

Update Failed: ERROR[10]: Magic byte is wrong, not 0xE9

And now no wifi or usb connection with Slimmelezer.
I contacted Marcel (zuidwijk.com) for suport.

29

Just adding here that the “use_address” brought my device online.
I have a DHCP reserve on my router. I could see it connected on my dashboard, but I couldn’t ping. I was able to see arp requests from the router, ESP replied that, but nothing happened afterwards.

Added “use_address” and use the same IP address I have reserved, done. pings get responses and Online on ESPHome Add-on on Home Assistant :slight_smile: Thanks @juan11perez

2 Likes
30

Hey team, this looks like an mDNS issue.
There’s two kinds of DNS services:

  • the normal IP based service (which the whole thread above is referencing)
  • a (newer) mDNS (multicast DNS) Multicast DNS - Wikipedia
    mDNS does not automatically propagate across different subnets and VLAN’s, so you need to have an mDNS repeater setup somewhere to have visibility across all networks.
    afaik home assistant comes with one, but it would also need network connectivity to each network and/or VLAN to make this work.
    Normally this is a function in your router, but not all of them have these capabilities

I’m struggling with a UniFi setup with 5 VLAN’s and 4 WiFi networks, the pain is real :grimacing:

31

I also have Unifi with 3 networks setup as VLANS. I cannot, for the life of me, get this figured out. I have several Tasmota devices setup without issue, but I can’t get an IP assigned to this ESPHome device. Please let me know if you figure it out!

32

Thank you! I came here much later, where esp-device.local did not work, but when I changed that to esp-device.my-domain.com in the yaml as you said, it worked.

1 Like
33

this worked for me too, Thanks.

also you can use the IP adress of the device but set it first as reserved in the rooter config to avoid any IP conflicts.

Regards.