As someone who has an Alarm Decoder GPIO chip that needs to be configured, I need to be able to modify the boot config file, turn off getty, and be able to access the device on serial0. Considering hass runs in a Docker image, I’m at a loss on the proper way to make these changes that will persist when updates happen. Additionally, there is no boot folder with a config or cmdline file. Any suggestions?
@goyney did you get this working yet?
I am getting ready to buy a AD2pi myself. I as anticipating this to be an issue, since the goal of Hass.io is to protect the OS from the user by creating a self contain environment.
I put my AD2PI on a pi zero, and connect to it over IP address I found that easier than running the entire stack on one device.
@flamingm0e So connecting over IP, there was no Hass.io issue.
Question, do you use the AD2pi webapp or notifications?
I trying to see if connecting over the network, uses up the webapp connection.
Once I had all my zones configured, I have no use for the web GUI. Home Assistant connects to it and has functionality to arm/disarm, read the sensors, etc. I have full control of everything I need from Home Assistant and node-red
I hear you. My only thought is backup access. Maybe not a good use case.
My main concern was Hass.io hiding too much that I needed to get it up and running. Even if I could run it on the same PI as HA, I would not. If we keep stacking on, one of these days the pile is going to fall.
Which still works fine. I access it over the network just like anything else on my network. Adding it to Home Assistant does not remove that functionality at all.
Which is why I would suggest an install on another device.
1 Like