There is an official docker image for AppDaemon that is completely unrelated to hassio. That image has the requirements.txt support built-in.
The hassio add-on is not based on this official image, that’s why it didn’t work.
2 Likes
i get the feeling that you hit the point there.
so lets make that clear.
hassio is an operating system like linux or windows
home assistant is a program like microsoft word or open office
an addon is a piece off code that makes it possible to use an existing program (like appdaemon) to install on hassio.
if you didnt install hassio (the operating system) but for example hasbian or just linux with home assistant, you shouldnt use hassio addons, but just install the right program.
how to install appdaemon the right way for your system can be found in the appdaemon docs.
https://appdaemon.readthedocs.io/en/latest/INSTALL.html
1 Like
@ReneTode You’re right, but @baz123 installed hassio on raspbian (IIRC) and then it’s probably worth using the add-on instead of plain docker.
correct, if hassio is installed then you need to install addons, but at that point also forget about docker 
because allthough its dockerbased, you dont have to do and understand with docker at all when using hassio.
and indeed the addon does work different from normal ways in more ways then i like
it sets token on its own, manipulates the appdaemon.yaml, replaces files that are normally in the config dir, etc.
there are many many times that i really am puzzled how they modified stuff and why and how those with hassio need to do things different.
and it doesnt help if people dont understand the difference between hassio and homeassistant or docker and addon. (and i understand there confusion)
Ok, I updated the docs to reflect the steps needed to configure hass-apps with the add-on.
1 Like
Which brings me back to the difference between HA & hassio. I installed, what I installed, from these instructions hassio-build/install at master · home-assistant/hassio-build · GitHub. It would seem I installed hassio inside a docker. What the pros and cons to that are obscure.
I had found previously that the hassio version seemed to be a more flexible solution wrt addons. Perhaps that has changed. TBH, the install instructions are far too biased towards Raspberry Pis - I am using a DietPi base as a VM, installed docker and then hassio. Works like a charm, but I stumbled across that solution rather than made an informed choice.
the difference between hassio and HA are like i described.
hassio is not a program, but an operatingsystem. HA is a program.
what you actually did is something like installing linux on a windows machine. inside some kind of wrapper (docker)
you probably try to say that you found that installing homeassistant on hassio seemed to be more flexible because hassio has addons, then installing home assistant on raspbian without hassio
hassio was never about flexibility, hassio is about easy install and doing the settings for you so that you dont need to think. but by letting a program set your settings, you lose the flexibility to do it yourself.
because its not a logical choice.
most people chose between this 2 options:
- make the RPI dedicated to homeassistant and install hassio as operating system
- chose for more flexibilty and install any kind if linux environment (raspbian, hassbian, raspbian light, etc.) and then just install home assistant.( in a venv or docker or just with pip)
you have chosen a difficult way to install an environment that is created to make it easy for users.
but it gives you options.
because you have hassio in a docker you can install the appdaemon addon inside hassio, but because you also have a rasbian environment you can also install appdaemon in a venv or as a normal docker.
and to make it difficult you could do those things all side by side.
its for you to find out what you like more.
@ReneTode There is one point I disagree with. Hassio is no operating system, it’s Home Assistant, an add-on store and a supervisor bundled together as a set of docker containers.
By saying to install hassio on a raspberry pi, you probably mean to install hassos, wich is an operating system containing docker + the hassio processes and some scripts for management.
If I wanted simplicity, I’d probably choosen hassos and let it do all the heavy lifting for me.
@baz123 Did you really install dietpi in a VM? What machine does this VM run on? Because if it’s a virtualized ARM system on a normal x86 machine, you should consider installing the official x86-64 OVA image of hassos instead. This will make performance a lot better.
i did write a whole piece and even when i was writing it i got confuesed , so its no wonder that people get confused 
most likely because it changes what it is.
according to the docs at this point: hassos is a part from hassio.
so you could say that hassio is hassos(an operating system) with 2 apps (homeassistant and addonstore) preinstalled.
and before hassos existed it was another cleaned out OS
and before that hassio was without os at all (which is probably what baz now uses
and before that we had hassbian which didnt have the addon store.
i would probably also chose the complete setup if i would go for hassio. (allthough the way baz did set it up is less restricted then the complete hassio version they have at the moment)
1 Like
Yeah, that’s all really confusing. At least hassos is the recommended way of installing hassio. And for the sake of flexibility, you can of course create your own add-ons as well that then run in docker on hassos.
I generally don’t like these highly specialized implementations because there’s a lot room for bugs and glitches. I recently managed to break a hassos running in KVM by just resetting the power. The whole file system was messed up afterwards and it didn’t boot anymore… bet this wouldn’t have happened with a rock solid Debian underneath.
At least I would always prefer a good old Debian/Fedora/whatever you feel comfortable with + a dockerized HA and AppDaemon over the hassos stuff, although the seamless atomic upgrades of hassos sound really nice.
One dumb question again… Is it possible to have a condition for the schedule to kick in like if temperature is below than x? Is it a question of the switch?I speak for heaty here because if it’s warm I don’t need to chedule … Because heaty and shedy kick in tu schedule no matter what the actual temp is.
@thundergreen Of course you can define a rule that aborts scheduling if some condition is met, but it should be the responsibility of your thermostats to decide whether they have to heat to reach the set target temperature or not.
I agree but apparently th thermostat in th ac is not that precise …that’s why I ask.so I have to write an Automation that switches of the switch for the schedule x if temp is higher than y?
@thundergreen You probably could, but that clearly is not the intended way. I mean, what is the purpose of a thermostat if it can’t heat to a given target temperature?
Don’t also…my house is 30 years old …and the AC is not that good
Yes…I use a custom component to control the AC via ir blasters (Xiaomi) …with all the Attributes needed
i got ubuntu and i dont like docker at all.
i prefer venv.
i got 2x HA and 4x AD all in their own venv.
@ReneTode Yes, that works as well of course. I just switched over from a venv-based setup to Docker last week and am testing how it performs. Apart from a 1 minute startup time on a Core i3-7100 I’m pretty happy with it, although just the Home Assistant docker image is 2.2GiB in size (yes, seriously). Maybe I’ll get back to the venvs later, but docker gives me some more flexibility in terms of macvlan networking so that all services can easily be placed in different subnets and firewalled correctly.
1 Like
I am using DietPi in a VM as the base - nice and lightweight
The problem I had with using a venv was working out how to update HA then it seemed very complicated to do so (that was a while ago though).
I don’t understand docker really but overall, it does just seem to work installing HA etc like this.