Seems? Try it and you will see, that the variables are entities with states as well.
Hej there!
I have the same Errors as jarg
No logs at any Addon.
Adguard without Ingress (like Grafana from Jarg)
ha addons logs a0d7b954_adguard
ha cli will show my all addons logs without new errors
First time i have this problems with 2022.5.5 maybe with the upgrade to HA OS 8.0?!
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: AdGuard Home
Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
Add-on version: 4.5.1
You are running the latest version of this add-on.
System: Home Assistant OS 8.0 (aarch64 / odroid-c2)
Home Assistant Core: 2022.5.5
Home Assistant Supervisor: 2022.05.2
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adguard.sh: executing...
[cont-init.d] adguard.sh: exited 0.
[cont-init.d] discovery.sh: executing...
[14:25:04] INFO: Successfully send discovery information to Home Assistant.
[cont-init.d] discovery.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:25:08] INFO: Starting AdGuard Home server...
2022/05/20 14:25:08.544334 [info] AdGuard Home, version v0.107.6
2022/05/20 14:25:08.605896 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/05/20 14:25:08.607935 [info] auth: initialized. users:0 sessions:0
2022/05/20 14:25:08.612397 [info] number of certs - 3
2022/05/20 14:25:08.612461 [info] got an intermediate cert
2022/05/20 14:25:08.612547 [info] got an intermediate cert
2022/05/20 14:25:08.947352 [info] Initialize web module
2022/05/20 14:25:10.050547 [info] AdGuard Home is available at the following addresses:
2022/05/20 14:25:10.050639 [info] Go to http://127.0.0.1:45158
2022/05/20 14:25:10.051055 [info] Go to https://xxxx.duckdns.org:421
[14:25:10] INFO: Starting NGinx...
2022/05/20 14:25:16.764958 [info] Starting the DNS proxy server
2022/05/20 14:25:16.765019 [info] Ratelimit is enabled and set to 20 rps
2022/05/20 14:25:16.765032 [info] The server is configured to refuse ANY requests
2022/05/20 14:25:16.765046 [info] DNS cache is enabled
2022/05/20 14:25:16.765077 [info] MaxGoroutines is set to 50
2022/05/20 14:25:16.765113 [info] Creating the UDP server socket
2022/05/20 14:25:16.765336 [info] Listening to udp://192.168.178.23:53
2022/05/20 14:25:16.765360 [info] Creating the UDP server socket
2022/05/20 14:25:16.765503 [info] Listening to udp://[xxx]:53
2022/05/20 14:25:16.765521 [info] Creating the UDP server socket
2022/05/20 14:25:16.765627 [info] Listening to udp://[xxxf]:53
2022/05/20 14:25:16.765642 [info] Creating the UDP server socket
2022/05/20 14:25:16.765742 [info] Listening to udp://172.30.32.1:53
2022/05/20 14:25:16.765759 [info] Creating a TCP server socket
2022/05/20 14:25:16.765873 [info] Listening to tcp://192.168.178.23:53
2022/05/20 14:25:16.765886 [info] Creating a TCP server socket
2022/05/20 14:25:16.765964 [info] Listening to tcp://[xxxx]:53
2022/05/20 14:25:16.765976 [info] Creating a TCP server socket
2022/05/20 14:25:16.766045 [info] Listening to tcp://[xxxx:53
2022/05/20 14:25:16.766059 [info] Creating a TCP server socket
2022/05/20 14:25:16.766120 [info] Listening to tcp://172.30.32.1:53
2022/05/20 14:25:16.766133 [info] Creating a TLS server socket
2022/05/20 14:25:16.766241 [info] Listening to tls://192.168.178.23:853
2022/05/20 14:25:16.766256 [info] Creating a TLS server socket
2022/05/20 14:25:16.766324 [info] Listening to tls://[xxxxx]:853
2022/05/20 14:25:16.766337 [info] Creating a TLS server socket
2022/05/20 14:25:16.766394 [info] Listening to tls://xxxx]:853
2022/05/20 14:25:16.766406 [info] Creating a TLS server socket
2022/05/20 14:25:16.766459 [info] Listening to tls://172.30.32.1:853
2022/05/20 14:25:16.766473 [info] Creating a QUIC listener
2022/05/20 14:25:16.774779 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2022/05/20 14:25:16.775063 [info] Listening to quic://192.168.178.23:784
2022/05/20 14:25:16.775096 [info] Creating a QUIC listener
2022/05/20 14:25:16.775535 [info] Listening to quic://[2xxxd7]:784
2022/05/20 14:25:16.775584 [info] Creating a QUIC listener
2022/05/20 14:25:16.776011 [info] Listening to quic://[fxxxxxf]:784
2022/05/20 14:25:16.776057 [info] Creating a QUIC listener
2022/05/20 14:25:16.776504 [info] Listening to quic://172.30.32.1:784
2022/05/20 14:25:16.777146 [info] Entering the tcp listener loop on [xxxxxx9f]:53
2022/05/20 14:25:16.778684 [info] Entering the UDP listener loop on [xxxx]:53
2022/05/20 14:25:16.778793 [info] Entering the DNS-over-QUIC listener loop on 192.168.178.23:784
2022/05/20 14:25:16.778843 [info] Entering the tcp listener loop on 172.30.32.1:53
2022/05/20 14:25:16.778870 [info] Entering the tls listener loop on 192.168.178.23:853
2022/05/20 14:25:16.778899 [info] Entering the tls listener loop on [2xxxxxx]:853
2022/05/20 14:25:16.778926 [info] Entering the tls listener loop on [fxxxxxf]:853
2022/05/20 14:25:16.778950 [info] Entering the tls listener loop on 172.30.32.1:853
2022/05/20 14:25:16.779001 [info] Entering the UDP listener loop on [xxxxxxx]:53
2022/05/20 14:25:16.779019 [info] Entering the UDP listener loop on 192.168.178.23:53
2022/05/20 14:25:16.779062 [info] Entering the UDP listener loop on 172.30.32.1:53
2022/05/20 14:25:16.779082 [info] Entering the tcp listener loop on 192.168.178.23:53
2022/05/20 14:25:16.779097 [info] Entering the tcp listener loop on [xxxxxxx]:53
2022/05/20 14:25:16.779115 [info] Entering the DNS-over-QUIC listener loop on 172.30.32.1:784
2022/05/20 14:25:16.779141 [info] Entering the DNS-over-QUIC listener loop on [2xxxx]:784
2022/05/20 14:25:16.779158 [info] Entering the DNS-over-QUIC listener loop on [fxxxx]:784
ha su logs
22-05-20 14:25:51 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 9 add-ons
22-05-20 14:25:51 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_core_configurator application
22-05-20 14:25:56 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-configurator with version 5.3.3
22-05-20 14:25:56 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:25:56 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_nodered application
22-05-20 14:25:57 INFO (SyncWorker_1) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:26:02 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/node-red/aarch64 with version 11.1.2
22-05-20 14:26:03 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_bitwarden application
22-05-20 14:26:05 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:26:08 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/bitwarden/aarch64 with version 0.16.0
22-05-20 14:26:08 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_a0d7b954_spotify application
22-05-20 14:26:11 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_a0d7b954_vscode application
22-05-20 14:26:14 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/spotify/aarch64 with version 0.11.0
22-05-20 14:26:15 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_15ef4d2f_esphome application
22-05-20 14:26:16 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:26:20 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/vscode/aarch64 with version 5.0.4
22-05-20 14:26:21 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on ghcr.io/esphome/esphome-hassio-aarch64 with version 2021.11.3
22-05-20 14:26:21 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_wireguard application
22-05-20 14:26:28 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/wireguard/aarch64 with version 0.6.0
22-05-20 14:26:28 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:26:29 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_cebe7a76_hassio_google_drive_backup application
22-05-20 14:26:29 INFO (SyncWorker_6) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:26:37 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on sabeechen/hassio-google-drive-backup-aarch64 with version 0.107.2
22-05-20 14:26:38 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_local_iddatalogger application
22-05-20 14:26:45 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on local/aarch64-addon-iddatalogger with version 0.2.1
22-05-20 14:26:46 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_76fa38ee_icantbelieveitsnotvaletudo application
22-05-20 14:26:53 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/poeschl/ha-icantbelieveitsnotvaletudo-aarch64 with version 3.6.2
22-05-20 14:26:57 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.4:1337 ssl:default [Connect call failed ('172.30.33.4', 1337)]
22-05-20 14:26:58 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:27:00 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
22-05-20 14:27:00 INFO (MainThread) [supervisor.core] Supervisor is up and running
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:00 INFO (MainThread) [supervisor.host.info] Updating local host information
22-05-20 14:27:00 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
22-05-20 14:27:00 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-05-20 14:27:00 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
22-05-20 14:27:00 INFO (MainThread) [supervisor.jobs] 'CheckDNSServerIPv6Errors.run_check' blocked from execution, no supervisor internet connection
22-05-20 14:27:00 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-05-20 14:27:00 INFO (MainThread) [supervisor.jobs] 'CheckAddonPwned.run_check' blocked from execution, no supervisor internet connection
22-05-20 14:27:00 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /dns/info access from a0d7b954_wireguard
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:00 INFO (MainThread) [supervisor.api.middleware.security] /backups/a4f0dc4e/info access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:03 INFO (MainThread) [supervisor.host.services] Updating service information
22-05-20 14:27:03 INFO (MainThread) [supervisor.host.network] Updating local network information
22-05-20 14:27:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
22-05-20 14:27:05 INFO (MainThread) [supervisor.jobs] 'CheckDNSServerFailures.run_check' blocked from execution, no supervisor internet connection
22-05-20 14:27:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-05-20 14:27:05 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-05-20 14:27:05 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-05-20 14:27:05 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-05-20 14:27:05 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-05-20 14:27:05 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-05-20 14:27:08 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-05-20 14:27:08 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-05-20 14:27:08 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
22-05-20 14:27:10 INFO (MainThread) [supervisor.api.middleware.security] /addons/77b2833f_timescaledb/info access from cebe7a76_hassio_google_drive_backup
22-05-20 14:27:21 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.4:1337 ssl:default [Connect call failed ('172.30.33.4', 1337)]
22-05-20 14:27:23 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.4:1337 ssl:default [Connect call failed ('172.30.33.4', 1337)]
22-05-20 14:27:24 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.4:1337 ssl:default [Connect call failed ('172.30.33.4', 1337)]
22-05-20 14:27:30 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with core_duckdns!
22-05-20 14:27:30 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_core_duckdns application
22-05-20 14:27:38 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-duckdns with version 1.14.0
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
22-05-20 14:28:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
22-05-20 14:28:32 INFO (MainThread) [supervisor.api.middleware.security] /core/logs access from a0d7b954_vscode
22-05-20 14:29:59 INFO (MainThread) [supervisor.api.middleware.security] /addons access from a0d7b954_vscode
22-05-20 14:30:34 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:30:34 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:30:52 INFO (MainThread) [supervisor.api.middleware.security] /core/update access from a0d7b954_vscode
22-05-20 14:31:19 INFO (MainThread) [supervisor.api.middleware.security] /addons/local_iddatalogger/logs access from a0d7b954_vscode
22-05-20 14:32:13 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from a0d7b954_vscode
22-05-20 14:32:31 INFO (MainThread) [supervisor.api.middleware.security] /addons/core_duckdns!/logs access from a0d7b954_vscode
22-05-20 14:32:32 INFO (MainThread) [supervisor.api.middleware.security] /addons/core_duckdns/logs access from a0d7b954_vscode
22-05-20 14:33:31 INFO (MainThread) [supervisor.api.middleware.security] /addons/77b2833f_timescaledb/logs access from a0d7b954_vscode
22-05-20 14:33:54 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on husselhans/hassos-addon-pgadmin4-aarch64 with version 2.0.0
22-05-20 14:34:10 INFO (MainThread) [supervisor.api.middleware.security] /dns/info access from 77b2833f_pgadmin4
22-05-20 14:34:49 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from a0d7b954_vscode
22-05-20 14:35:46 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:35:46 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:37:20 INFO (MainThread) [supervisor.api.middleware.security] /addons/core_duckdns/logs access from a0d7b954_vscode
22-05-20 14:39:00 INFO (MainThread) [supervisor.api.middleware.security] /addons/a0d7b954_adguard/logs access from a0d7b954_vscode
22-05-20 14:40:48 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:40:48 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:40:51 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:40:51 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:41:16 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from a0d7b954_vscode
22-05-20 14:43:08 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-600' coro=<_websocket_forward() done, defined at /usr/src/supervisor/supervisor/api/ingress.py:280> exception=ConnectionResetError('Cannot write to closing transport')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/api/ingress.py", line 287, in _websocket_forward
await ws_to.send_bytes(msg.data)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_ws.py", line 315, in send_bytes
await self._writer.send(data, binary=True, compress=compress)
File "/usr/local/lib/python3.9/site-packages/aiohttp/http_websocket.py", line 688, in send
await self._send_frame(message, WSMsgType.BINARY, compress)
File "/usr/local/lib/python3.9/site-packages/aiohttp/http_websocket.py", line 653, in _send_frame
self._write(header + message)
File "/usr/local/lib/python3.9/site-packages/aiohttp/http_websocket.py", line 663, in _write
raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport
22-05-20 14:43:10 INFO (MainThread) [supervisor.api.middleware.security] /addons/a0d7b954_adguard/logs access from a0d7b954_vscode
22-05-20 14:45:56 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:45:57 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:51:02 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret red_secret
22-05-20 14:51:02 INFO (MainThread) [supervisor.homeassistant.secrets] Request secret root_pass
22-05-20 14:53:21 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from a0d7b954_vscode
You appear to have no internet connection. I donât know for certain if that breaks your ability to see the logs from the UI but I do know that breaks a lot of important things (as you can see from how many times that warning appears in your log). I would start there, what does ha network info say?
That must be the first few minutes.
I work exclusively via the Internet with my HA instance. Not via the local IP.
Network Info looks normal until âsupervisor_internet: falseâ
few minutes ago âsupervisor_internet: trueâ
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: true
enabled: true
interface: eth0
ipv4:
address:
- 192.168.178.23/24
gateway: 192.168.178.1
method: auto
nameservers:
- 192.168.178.23
ipv6:
address:
- xxxxx/64
- xxxxx/64
- xxxxx/64
gateway: xxxxx
method: auto
nameservers:
- xxxx
primary: true
type: ethernet
vlan: null
wifi: null
supervisor_internet: true
Since today Chrome will show me a pishing infomartion at my ha url
Seems like itâs IPV6 itâs complaining about ( no wonder, as i doubt your system using this ) , on the other hand, i donât have this Error, so maybe some Network Config somewhere in your setup
Did you by any chance âdisabledâ IPV6 on the interface ? ⌠and are you sure
- 192.168.178.23
is the nameserver you want to use ? , in normal cases it would be "
gateway: 192.168.178.1 "
Edit: i assumed " 192.168.178.23 " is your HA -instance, but maybe you have/use some kind of ânameserverâ there, on some port, and then of-cause that you have configured your HA to use this, but im not familiar with this âSetupâ
Where did you see DNS_SERVER_IPV6_ERROR? I saw this in their logs:
But that doesnât actually mean that check is failing. It wasnât run at all because supervisor didnât have internet so it couldnât.
So wait @dasTholo is it fixed now? Or are you still unable to access the logs in the UI?
This doesnât really have anything to with HA. HA just serves up the certificate you tell it to if you are using itâs SSL options. Itâs your responsibility to manage that certificate and ensure it meets all validity requirements of your browser and whatever other clients you access HA from. (Note: Unless you use cloud, then itâs Nabu Casaâs responsibility to ensure you never see that error)
It also shouldnât block anything in a browser. You can tell the browser to ignore the error for now and figure out how to fix that later.
Iâm guessing they are trying to use https with the IP address. In which case adding a browser exception is the only option.
ok, my mistake, didnât read all related ( just skimmed there i guess ), and then saw the âHa net infoâ which to me seemed âstrangeâ, partly the IPV6 -config, and that he point his DNS to HA, thou as mentioned i have no experience from on that part, as i use my Router, beside mDNS might have a role
. No Duck, or other solution, and as you know, i use IPâs (where i can) not hostnames 
Yes, seems - I installed it via HACS but its seems to be not working. According to the documentation I should see var.set listed in service calls, but it is not there. that is good if they are modelled as entities with states, but that isnâs shown in any of the examples, they all use templates. Seems like the documentation could be improved a little.
Wow! I have no idea where to start. I think this is one of the greatest releases ever.
I donât know which of my ideas to implement first. Way too many new automation features.
Big thanks!
2 Likes
No is still does not work even if the supervisor has internet.
My HA is the DNS Server with the Adguard Addon. 192.168.178.1 is the Modem (Fritz Box).
SSL would be created with the duckdns Addon. Until yesterday it was all okay.
BUT Upgrade HA OS 8.1 fix my Log Issues!!!
Addons Logs are back
/config/system_health
2 Likes
Apologies if this has already been discussed (I havenât trawled through ~550 posts), but I have to express my disappointment / frustration that the SQL integration has gone the way of GUI config. I get why GUI config is a good thing and why making it easier for less technically inclined users is to the benefit of us all.
But certain integrations (the SQL integration being a classic example) will always be limited to advanced users; the shift to GUI and away from YAML is unequivocally a step backwards for those users. SQL queries are code and should be managed as code. We lose the ability to track changes through source control, structure related config into packages and simple things like mono-spaced fonts and access to conveniences like secrets to store password strings.
What I really donât understand is why it must be one or the other. Why canât YAML config be used alongside GUI config? This works for automations, why canât it work for integrations too? Surely it would be a win / win.
Maybe Iâm missing something, but this change just doesnât make sense to me.
5 Likes
Search for SQL on this thread and youâll find the answers to your questions.
Thanks Pieter - fair call and good suggestion. Now Iâve been through the thread and I donât find the answers to my question - only statements that it has been done, move on. As well as a bunch of frustrated people like me who are baffled by the change.
Please donât get me wrong - I love HA and the devs and all the great work they do. I get the origin of the decision why it is (generally) a good idea. But in this case it feels like following through on a general architectural decision that doesnât actually make sense in this context.
More than anything, I am still none the wiser as to why it must be GUI or YAML but not both.
2 Likes
The ADR states that the code owners can do what they want with the integration. They are allowed to maintain both yaml and gui. The code owner of that integration didnât want to maintain both.
They are allowed to do what they want or are they forced to implement GUI and then only have the choice of additionally supporting yaml or not?
I mean, was there not the new requirement forcing GUI whether the code owner wants to or not?
1 Like
Only new integrations have to add the ui. Any upgrades to existing integrations are up to the code owner.