I am very new to home assistant only installing about a week ago, since the latest update I am unable to access any of my add-ons and am also unable to access the supervisor tab.
HA is installed on a Raspberry Pi4. Really unsure how I am going to fix this - any advice would be welcome.
I am not super technical so hopefully there is a simple solution.
Quick: reboot the device, might not work
Not quick: Create a separate thread on this forum, or join discord https://discord.gg/c5DvZ4e
In the new thread, or on discord, provide logs from the help page http://IP_OF_PI:4357
Thanks for the fast response, have tried several reboots with no success. Will try discord or new thread option.
Many users of addon PAI (Paradox Alarm) have reported issues since Supervisor 249 update :
I’ve tried to downgrade Supervisor to version 247 yesterday, it worked but automatically updated back to 249. Is there a way to prevent this automatic update temporarily ?
Thx.
The author of that add-on is working on a fix
1 Like
I’ve just seen your answer on github ! Thanks ! 
Still thinks my stuff is broken:
20-10-22 12:05:04 ERROR (MainThread) [supervisor.utils.gdbus] Can't parse '[{"connection": {"autoconnect-priority": -999, "id": "eth0", "permissions": [], "timestamp": 1603368129, "type": "802-3-ethernet", "uuid": "bbf6ed2c-6b10-3bdd-a4e9-7267dc2ee883"}, "802-3-ethernet": {"auto-negotiate": false, "mac-address": [220, 166, 50, 101, 87, 26], "mac-address-blacklist": [], "s390-options": {}}, "ipv4": {"address-data": [{"address": "192.168.12.10", "prefix": 23}], "addresses": [[168601792, 23, 4262308032]], "dns": [51161280, 84715712], "dns-search": [], "gateway": "192.168.13.254", "method": "manual", "route-data": [], "routes": []}, "proxy": {}, "ipv6": {"address-data": [{"address": "2001:470:792d:1:12::10", "prefix": 64}], "addresses": [[[32, 1, 4, 112, 121, 45, 0, 1, 0, 18, 0, 0, 0, 0, 0, 16], 64, [32, 1, 4, 112, 121, 45, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1]]], "dns": [[32, 1, 4, 112, 121, 45, 0, 1, 0, 18, 0, 0, 0, 0, 0, 3], [0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05]], "dns-search": ["delaars12.loc"], "gateway": "2001:470:792d:1::1", "method": "manual", "route-data": [], "routes": []}}]
': '({'connection': {'autoconnect-priority': <-999>, 'id': <'eth0'>, 'permissions': <@as []>, 'timestamp': <uint64 1603368129>, 'type': <'802-3-ethernet'>, 'uuid': <'bbf6ed2c-6b10-3bdd-a4e9-7267dc2ee883'>}, '802-3-ethernet': {'auto-negotiate': <false>, 'mac-address': <[byte 0xdc, 0xa6, 0x32, 0x65, 0x57, 0x1a]>, 'mac-address-blacklist': <@as []>, 's390-options': <@a{ss} {}>}, 'ipv4': {'address-data': <[{'address': <'192.168.12.10'>, 'prefix': <uint32 23>}]>, 'addresses': <[[uint32 168601792, 23, 4262308032]]>, 'dns': <[uint32 51161280, 84715712]>, 'dns-search': <@as []>, 'gateway': <'192.168.13.254'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>, 'routes': <@aau []>}, 'proxy': {}, 'ipv6': {'address-data': <[{'address': <'2001:470:792d:1:12::10'>, 'prefix': <uint32 64>}]>, 'addresses': <[([byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10], uint32 64, [byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01])]>, 'dns': <[[byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03], [0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05]]>, 'dns-search': <['delaars12.loc']>, 'gateway': <'2001:470:792d:1::1'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>, 'routes': <@a(ayuayu) []>}},)
' - Expecting ',' delimiter: line 1 column 858 (char 857)
20-10-22 12:05:04 WARNING (MainThread) [supervisor.host.network] Can't update network information!
Something is not parsed correctly for your IPv6 DNS servers @SandJ open an issue https://github.com/home-assistant/supervisor/issues/new and add the logs there, as well a description of your setup, and if possible the configuration files for Network Manager and output of nmcli
Is there any downside to simply ignoring. I’m 100% fine w/ this route vs. messing w/ config settings. “If it ain’t broke, don’t fix it”. Just trying to ensure that it “ain’t broke” currently 
As far as I can tell, everything seems to be working fine, just getting the Operating System and Network Manager warning messages (posted above fwiw):
Which means, things can break/stop working.
I had a similar problem with Covid-19 not working. In the end I added an extra line for DNS to /etc/docker/daemon.json and then everything started working again.
{
"log-driver": "journald",
"dns": [ "8.8.8.8", "8.8.4.4", "Your Own Local DNS if you have one" ],
"storage-driver": "overlay2"
}
Hi all,
Now that we have rate limits on docker hub I am starting to get really annoyed with the impact of that to my setup. Of course I am considering paying docker for this but frankly speaking I am not liking that idea much because I don’t think the service this provides is priced fairly. Like I can get oodles of storage for a few dollars a month with Google, AWS etc and yet just for hosting and serving some metadata I’d have to pay Docker much more. So before I go there i am willing to burn some cycles and setup a local mirror on my home network. I would be doing that on my Qnap NAS and I am considering using Quay for this.
But before I put in the effort I’d like to know how hardcoded the docker hub is for homeassistant. If I mirror all relevant content including core homeassiant etc and add my local mirror to the supervisor will everything work? I would basically block my RPI running homeassistant from reaching docker after this and only have my mirror sync every 24 hours or so.
Please advise if this is possible and if anyone has tried this already I am keen learn from your work.
Many thanks!