filippos
August 17, 2019, 1:57pm
1
Im experiencing a bizzare issue.
tom_l
August 17, 2019, 2:12pm
2
Possibly mDNS issues. One of the reasons I use static IP addresses for my ESPhome sensors.
Try restarting your router. Otherwise hopefully they are accessible so you can connect using the USB serial method.
filippos
August 17, 2019, 2:16pm
3
humm i thought the same but when i ping device.lan in the terminal i get the correct local ip… isnt that strange that hassio cant get the local ip? and that since yesteday… before that it worked fine.
tom_l
August 17, 2019, 2:17pm
4
pinging ain’t mDNS. Try the router restart.
smoke.007
August 17, 2019, 2:25pm
5
Looks like there’s a DNS issue with the 0.97.2 update. I’m going to just restore from backup from before the update for now.
opened 08:43PM - 16 Aug 19 UTC
closed 02:09PM - 23 Aug 19 UTC
**Home Assistant release with the issue:**
0.97.2
**Operating environment (H… assOS/Generic):**
HASS.io running on Raspberry PI 3B
```
arch: armv7
channel: stable
hassos: null
homeassistant: 0.97.2
hostname: null
logging: info
machine: raspberrypi3
supervisor: "179"
supported_arch:
- armv7
- armhf
timezone: Europe/Berlin
```
**Supervisor logs:**
```
19-08-16 20:38:15 INFO (MainThread) [__main__] Initialize Hass.io setup
19-08-16 20:38:15 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armhf-hassio-supervisor with version 179
19-08-16 20:38:15 INFO (SyncWorker_0) [hassio.docker.supervisor] Connect Supervisor to Hass.io Network
19-08-16 20:38:17 INFO (SyncWorker_0) [hassio.docker.interface] Cleanup images: ['homeassistant/armhf-hassio-supervisor:178']
19-08-16 20:38:18 INFO (MainThread) [__main__] Setup HassIO
19-08-16 20:38:18 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/armhf-hassio-dns with version 1
19-08-16 20:38:18 INFO (MainThread) [hassio.dns] Update resolv from Supervisor
19-08-16 20:38:18 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1
19-08-16 20:38:18 INFO (MainThread) [hassio.misc.forwarder] Start DNS port forwarding to 172.30.32.3
19-08-16 20:38:18 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error connecting: Could not connect: No such file or directory\n'
19-08-16 20:38:18 WARNING (MainThread) [hassio.dbus.systemd] Can't connect to systemd
19-08-16 20:38:18 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1
19-08-16 20:38:18 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error connecting: Could not connect: No such file or directory\n'
19-08-16 20:38:18 WARNING (MainThread) [hassio.dbus.hostname] Can't connect to hostname
19-08-16 20:38:18 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /
19-08-16 20:38:18 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error connecting: Could not connect: No such file or directory\n'
19-08-16 20:38:18 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc
19-08-16 20:38:18 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
19-08-16 20:38:18 INFO (MainThread) [hassio.host.apparmor] AppArmor is not enabled on host
19-08-16 20:38:18 INFO (SyncWorker_2) [hassio.docker.interface] Attach to homeassistant/raspberrypi3-homeassistant with version 0.97.2
19-08-16 20:38:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/cebe7a76 repository
19-08-16 20:38:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/git/a0d7b954 repository
19-08-16 20:38:19 INFO (MainThread) [hassio.store.git] Load add-on /data/addons/core repository
19-08-16 20:38:20 INFO (MainThread) [hassio.store] Load add-ons from store: 60 all - 60 new - 0 remove
19-08-16 20:38:20 INFO (MainThread) [hassio.addons] Found 10 installed add-ons
19-08-16 20:38:20 INFO (SyncWorker_5) [hassio.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 6.2
19-08-16 20:38:20 INFO (SyncWorker_6) [hassio.docker.interface] Attach to hassioaddons/grafana-armv7 with version v2.2.3
19-08-16 20:38:20 INFO (SyncWorker_0) [hassio.docker.interface] Attach to sabeechen/hassio-google-drive-backup-armv7 with version 0.98.2
19-08-16 20:38:20 INFO (SyncWorker_13) [hassio.docker.interface] Attach to hassioaddons/influxdb-armv7 with version v3.1.2
19-08-16 20:38:20 INFO (SyncWorker_8) [hassio.docker.interface] Attach to homeassistant/armv7-addon-mosquitto with version 5.0
19-08-16 20:38:20 INFO (SyncWorker_7) [hassio.docker.interface] Attach to homeassistant/armv7-addon-duckdns with version 1.9
19-08-16 20:38:20 INFO (SyncWorker_3) [hassio.docker.interface] Attach to homeassistant/armv7-addon-git_pull with version 7.4
19-08-16 20:38:20 INFO (SyncWorker_0) [hassio.docker.interface] Attach to homeassistant/armhf-addon-bluetooth_bcm43xx with version 2.3
19-08-16 20:38:20 INFO (SyncWorker_10) [hassio.docker.interface] Attach to homeassistant/armv7-addon-check_config with version 2.2
19-08-16 20:38:20 INFO (SyncWorker_5) [hassio.docker.interface] Attach to homeassistant/armhf-addon-deconz with version 3.1
19-08-16 20:38:20 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-08-16 20:38:20 INFO (MainThread) [hassio.snapshots] Found 10 snapshot files
19-08-16 20:38:20 INFO (MainThread) [hassio.discovery] Load 2 messages
19-08-16 20:38:20 INFO (MainThread) [hassio.ingress] Load 2 ingress session
19-08-16 20:38:20 INFO (MainThread) [__main__] Run Hass.io
19-08-16 20:38:20 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
19-08-16 20:38:20 INFO (MainThread) [hassio.addons] Phase 'initialize' start 1 add-ons
19-08-16 20:38:21 INFO (SyncWorker_19) [hassio.docker.interface] Clean addon_core_bluetooth_bcm43xx application
19-08-16 20:38:29 INFO (SyncWorker_19) [hassio.docker.addon] Start Docker add-on homeassistant/armhf-addon-bluetooth_bcm43xx with version 2.3
19-08-16 20:38:30 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-08-16 20:38:34 INFO (MainThread) [hassio.core] Hass.io reboot detected
19-08-16 20:38:34 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
19-08-16 20:38:34 INFO (MainThread) [hassio.core] Hass.io is up and running
19-08-16 20:38:58 INFO (MainThread) [hassio.api.security] /homeassistant/restart access from core_ssh
19-08-16 20:38:58 INFO (SyncWorker_13) [hassio.docker.interface] Restart homeassistant/raspberrypi3-homeassistant
19-08-16 20:39:00 ERROR (MainThread) [hassio.homeassistant] Error on call https://172.30.32.1:8123/api/states/binary_sensor.snapshots_stale: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
19-08-16 20:39:00 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/binary_sensor.snapshots_stale
19-08-16 20:39:26 ERROR (MainThread) [hassio.homeassistant] Error on call https://172.30.32.1:8123/api/states/binary_sensor.snapshots_stale: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
19-08-16 20:39:26 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/binary_sensor.snapshots_stale
19-08-16 20:39:46 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-08-16 20:40:15 INFO (MainThread) [hassio.api.security] /dns/logs access from core_ssh
19-08-16 20:41:17 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh
```
**Description of problem:**
See this thread in the forum: https://community.home-assistant.io/t/name-resolution-problem-since-0-97-2/132201
Looks like several people have issues with the HASS internal DNS system. Even after updating the DNS server to my local router, the internal name resolution in HASS still fails.
```
hassio dns options --servers dns://192.168.178.1
````
```
ERROR (MainThread) [homeassistant.components.mjpeg.camera] Error getting new camera image: Cannot connect to host archpi.fritz.box:8081 ssl:None [Name does not resolve]
````
This morning I restarted hass.io (currently running 0.97.2) and to my surprise all my Esphome.io devices went unavailable in home assistant. I must have done this hundreds of times over the last 6 months and haven’t had this issue. I started looking around on the forum and found a post someone made about their Esphome device’s IP changing. I tried removing the integration for one (of three) and adding it back with the local DNS name and it wouldn’t find it. When I used the IP, however, it found …
filippos
August 17, 2019, 2:26pm
6
still not working.http://revowebcam.lan or https://hassio.lan:8123
tom_l
August 17, 2019, 2:27pm
7
@smoke.007 That won’t help. The supervisor will automatically update again.
@filippos could be due to the supervisor DNS issue. Do you have pi-hole or some other DNS service locally?
filippos
August 17, 2019, 2:28pm
8
@smoke.007 is right… hopefully the new update will come soon with this bugfix
filippos
August 17, 2019, 2:29pm
9
yes i have a piHole in a dedicated raspbian… conflict?
filippos
August 17, 2019, 2:31pm
11
but the dhcp is in my router, not my pihole.
smoke.007
August 17, 2019, 2:31pm
13
FYI, I don’t have piHole installed, but still having the same DNS issue keeping ESPHome from being able to resolve proper IPs for ESPHome devices.
filippos
August 17, 2019, 2:32pm
14
i dont think its the pihole.
tom_l
August 17, 2019, 2:32pm
15
I just checked - (it’s working for me) but that’s because I have static ips. Doh.
tom_l
August 17, 2019, 2:33pm
16
The hassio supervisor updated automatically in the last 24 hours. You don’t have any control over that.
filippos
August 17, 2019, 2:35pm
17
ohhh nooo, we need to have this fixed asap… most of my automations and entities are not working atm
tom_l
August 17, 2019, 2:36pm
18
There are solutions, but they only work until you restart HA. Let me see if I can find a link.
filippos
August 17, 2019, 2:39pm
19
unfortunately those are half measures until the devs restore this issue.
tom_l
August 17, 2019, 2:44pm
20