Said above:
Okay, but still need the versions. 
It is just that when I try to call “ha dns downgrade” then I get an error, so I would like to know what setup KKen94 has.
1 Like
You can’t even connect to local resources, check your NIC and ethernet-cable, And run " ha net info " in the console or terminal
As Wally mentioned DHCP, it either doesn’t get an IP, or you have set static in HA, and after the power-cut who knows your Router was resetted to another subnet, or gave the IP of HA to another device, because you didn’t have reservation setting
Hassio has its own IP as everything in my house. Nothing changed router side, cause as I said if I run ha dns downgrade it works for some hours.
That wasn’t what i wanted to hear “run ha net info”
Check your Router, and cables, don’t be stubborn
36 ERROR (SyncWorker_8) [homeassistant.components.fritzbox_callmonitor.sensor] Cannot connect to 192.168.1.1 on port 1012: [Errno 111] Connection refused
2024-03-07 12:21:15.634 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'ClientConnectorError'
2024-03-07 12:21:15.703 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2024-03-07 12:21:19.138 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform songpal is taking over 10 seconds.
2024-03-07 12:21:20.130 WARNING (MainThread) [homeassistant.components.songpal.media_player] [Soundbar(http://192.168.1.7:10000/sony)] Unable to connect
2024-03-07 12:21:20.175 ERROR (MainThread) [homeassistant.components.mqtt.client] Failed to connect to MQTT server due to exception: [Errno -3] Try again
2024-03-07 12:21:20.300 WARNING (MainThread) [homeassistant.components.media_player] Platform songpal not ready ye
Something is killing you network , Mr fritz?
Yes, that would be a good help, as it connection issues, http/https, IP-ban list etc. etc.
EDIT: Try to roll back to previous, working HA version ( To i.e exclude Python-version 3.12 issues )
Are you running Portainer or having multiple networks connected?
Keep calm phenomenon, I didn’t see your message.
This is the ha net info
docker:
address: 172.30.32.0/23
dns: 172.30.32.3
gateway: 172.30.32.1
interface: hassio
host_internet: true
interfaces:
- connected: false
enabled: false
interface: wlan0
ipv4:
address: []
gateway: null
method: disabled
nameservers: []
ready: false
ipv6:
address: []
gateway: null
method: disabled
nameservers: []
ready: false
mac: B8:27:EB:D0:9D:5E
primary: false
type: wireless
vlan: null
wifi: null
- connected: true
enabled: true
interface: eth0
ipv4:
address:
- 192.168.1.37/24
gateway: 192.168.1.1
method: static
nameservers:
- 192.168.1.1
ready: true
ipv6:
address:
- fd00::24a8:aa1e:64c0:a92b/64
- fe80::6721:dffc:7dbb:b886/64
gateway: null
method: auto
nameservers:
- fd00::1eed:6fff:feb0:b28f
ready: true
mac: B8:27:EB:85:C8:0B
primary: true
type: ethernet
vlan: null
wifi: null
supervisor_internet: true
@WallyR Ever had portainer, but on another machine and hassio is not on that docker
I still suggest to try to “restore from backup” to i.e 2024.02.04, to exclude update-causes
Ohh, you got IPv6 set up.
IPv6 have priority over IPv4 and you have an IPv6 nameserver listed.
Make sure that one can be reached and it works.
fd00 is a link-local address (somewhat equal to the local IPv4 NAT subnets, like 192.168.x.x), so it is a device on your local net.