Hi,
i had a good running system - yesterday an update brokes my whole setup ;-(
After getting a backup ssd with a running OS & HA Docker environment my setup gets broken again by selfupdating.
I dint want that i want to update when i am prepared for it.
Now after some hours and rebuiling my setup from scratch i’ve got Supervisor 214 even when my configuration.yaml looks like this:
automation:
config:
frontend:
history:
logbook:
map:
person:
script:
ssdp:
sun:
system_health:
Take a look in the supervisor system log. It makes a regular check for the latest, you can block that site (if you have the capability in your router/firewall) and prevent the system from even seeing the update.
https://version.home-assistant.io/stable.json
You also have
https://version.home-assistant.io/beta.json and https://version.home-assistant.io/dev.json
Hi,
after reading all the similar posts with no real working solution.
I “think” i’ve got it.
be aware its getting dirty thx Frenck to forcing me into this kind of dirty things;-)
docker exec -it hassio_supervisor /bin/bash
find / -name "*.json" -exec sed -i 's|https://home-assistant.io/hassio|https://home-assistant.notio/toupdatehassiowithoutmyconfirmation|g' {} \;
exit
be aware its dirty and you may loose some security and you never gettin the newest hippest stuff unless you remove hassio_supervisor and pull it from docer or you reverse the sed back to original.
shit…
even after downloading the stable.json to my apache - changing all the versions to my running setup and changinging the url from https://home-assistant.io/hassio to my local apache…
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4cb6e3128303 homeassistant/amd64-hassio-audio:9 “/init” 5 minutes ago Up 5 minutes hassio_audio
420793ecd047 homeassistant/amd64-hassio-cli:24 “/init /bin/bash -c …” 5 minutes ago Up 5 minutes hassio_cli
465d36928ae1 homeassistant/amd64-hassio-supervisor “/init” 5 minutes ago Up 5 minutes hassio_supervisor
thats very bad not to say it sucks
any other dirty thinking/solution available? XD
just found /usr/src/supervisor/setup.py
right now my clonezilla is working and after that i disable internet and do do a full
find -type -f -exec sed -i ‘s|https://home-assistant.io/hassio|whatever’ {} ; to ALL of the running dockers.
I will find a way - i am very pissed and i already was a good hacker in the old days when i was much younger.
Not getting an answer from the official is not a solutution but it keeps me to solve it by my own.
Just remember there are many other unanswered threads with the same “wish” / “feature request”
Exactly and I am sure there’s an explanation for it, why supervisor is still automatically updating itself.
But nonetheless I’d prefer to have control over whether I update a certain component of Home Assistant due to possibly things breaking and eventually harder to fix things.
I was thinking, I could block these URL’s with AdGuard. The system wont be able to resolve it then.
https://version.home-assistant.io/stable.json
https://version.home-assistant.io/beta.json and https://version.home-assistant.io/dev.json
hmm adguard is the same “args” like the audio alsapulse fix addon
Why should we use something on top to prevent a simple task instead of a simple
if youresure then disable update fi somewhere?
i have to say goodbye
my draytek router is now in charge and home-assistant.io isnt aviable on my private LAN anymore
cheers
Lol. The hate… you could also create a seperate VLAN. Block home-assistant.io there and allow traffic between your regular network (vlan) and traffic to your vlan which contains your home assistant installation.
But I guess you wont read this anymore. Maybe you get notified through email if i tag you @Jan.Schmidt
But good luck! Cheers~
yupp ther are many ways to shear the sheep.
since my 24/7 I7 16GB Monster was already very safe in terms on networking (ioT) on a separate WLAN not exposed to Internet no NAT just vpn - i dont care.
sadly i found two different dns clients pointing to external servers and some other stuff
But i had to leave because i cant help anyone cant contribute anything cause i decided to get stuck on
btw: blocking home-assistant.io isnt working you need to block docker.io as well.
but everfy ~60 mins some error fills the log
thx for your time -maybe
@Burningstone
thx for pointing me into the right way:
My first way was to get rid of the update - now after i got it to work thx again for pointing me to main issue.
So the solution how t get rid of the selfupdater is much more simpler than my first approach.
The solution is not get rid of the updater - get rid of the supervisor.
I didnt need it - my system runs fine without because i only use basic stuff.
eg if your on supervisor v 193
sudo systemctl stop hassio-apparmor.service
sudo systemctl disable hassio-apparmor.service
sudo systemctl stop hassio-supervisor.service
sudo systemctl disable hassio-apparmor.service
docker container rm hassio_supervisor
docker container rm hassio_dns
adding a cronjob like
@reboot docker start homeassistant
if this post does harm anyone - please feel free to tell the team they should delete my account and all of my postings and ban me for the rest of my life or the eol of this project whatever comes first.
Why even say this? This is the crap @nickrout was talking about. Word of advice, leave out the negativity and you won’t get negativity towards you.
@petro
i’ve been warned twice and in my research i found the Team want the supervisor to be always up to date, and i dont know if this does harm any of your rules.
No i am not “negativity” i am unsure whats right what wrong - because if the (my) solution is so simple - why isnt any hint that this is possible - (sorry if there is any hint to this and i didnt found it)
Believe me - I am very happy with my running system and HA and i feel much more comfortable right now because now i can put my brain into my setup and didnt have to worry about unattended updates and whats wrong because if something broke i know what i’ve changed and reverse it.
The only thing i missed (for a very short time) - was the “backup” - but even that is easy
docker image save homeassistant/qemux86-64-homeassistant -o /media/backup/ha_`date +'%Y'.'%m'.'%d'`.tar
cheers
There are no rules other than don’t be a jerk to people. It’s normal forum etiquette. Telling people to how to work around an issue isn’t going to flag anything. The reason you’re getting warnings is because you’re being a jerk. Plan and simple.
Just saying, I think it would have been easier to make a backup of your config. Uninstall Home Assistant Supervised (formerly called hass.io), install Home Assistant Core in docker and then reload your backup.
For your information, you will not be able to use add-ons anymore, but I assume you already know that.