mdns provides a response for 1min then fails.

amerikiwi93 commented 2 years ago

The problem

ESP8226 responds to mdns (ss01s-light.local) requests after a few seconds then goes does not respond. Cannot download from addon, however lovelace works. Requres use_address: 192.168.1.123 in the wifi section.

Immediately after the update:

root@OpenWrt:~# avahi-browse --resolve -at
...
= br-lan IPv4 ss01s-light                            _esphomelib._tcp     local
   hostname = [ss01s-light.local]
   address = [192.168.1.173]
   port = [6053]
   txt = ["version=2021.10.2" "mac=8cce4eef67d3" "platform=ESP8266" "board=esp01_1m"]
...
root@OpenWrt:~#

Approx 1min later

root@OpenWrt:~# avahi-browse --resolve -at
...
Failed to resolve service 'ss01s-light' of type '_esphomelib._tcp' in domain 'local': Timeout reached
...
root@OpenWrt:~#

Might be related to #2616 or "Fix MDNS for ESP8266 devices 2571"

Which version of ESPHome has the issue?

2021.10.X

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2021.10.6

What platform are you using?

ESP8266

Board

treatlife-ss01s

Component causing the issue

mdns

Example YAML snippet

wifi:
  ssid: !secret wifi_ssid #wifi_iot_ssid
  password: !secret wifi_password #wifi_iot_password

  ap:
    ssid: ${device_name} AP
    password: !secret esphome_fallback_ap_password

  #use temporary static address for uploads
   use_address: 192.168.1.123

#enable WiFi hotspot after 1min of no wifi connectivity
captive_portal:

# Enable logging
logger:

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

ota:
  password: !secret esphome_ota_password

Anything in the logs that might be useful for us?

No response

Additional information

Only have ESP8226 devices to test on.

probot-esphome[bot] commented 2 years ago

Hey there @esphome/core, mind taking a look at this issue as it has been labeled with an integration (mdns) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

oxan commented 2 years ago

What is the actual version that gives this behaviour? 2021.10.0 vs 2021.10.1 makes quite a difference here.

amerikiwi93 commented 2 years ago

It happens on 2021.10.0 & 2021.10.1

On Thu, Oct 28, 2021, 16:41 Oxan van Leeuwen @.***> wrote:

What is the actual version that gives this behaviour? 2021.10.0 vs 2021.10.1 makes quite a difference here.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/esphome/issues/issues/2623#issuecomment-954196494, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF3D2BBVUTFNSJ2M76CKO33UJG7SNANCNFSM5GTJZ4DQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

davidcoulson commented 2 years ago

I am having a similar issue on a ESP32 using: ESPHome version 2022.1.2 compiled on Jan 30 2022, 10:21:04

patagonaa commented 2 years ago

If you're using Unifi APs, this (or something similar) might be your issue: https://github.com/esphome/issues/issues/3003#issuecomment-1047274557

esphome / issues