From: Pancho.Jones@protonmail.com
On 2/13/25 12:15, Theo wrote:
> Adrian wrote:
>> So far as I've been able to find out, HA is only installed as an image
>> on the SD card (using the RPI Imager), rather than manually installed on
>> an existing Pi image (e.g. apt install ...), so that means that the Pi
>> can only be used for what HA allows you to do. Therefore, one downside
>> (for me) with HA is that I don't seem to be able to gain SSH access to
>> the PI. I can access it via the web interface, and I can install a ZSH
>> shell on it, but that is in (I think) a Docker Container. What I would
>> like to be able to do, which I can with my other Pis, is to run regular
>> health check stuff, CPU temp, free memory, free card space that sort of
>> stuff. I can do that from the Docker Container, but I can't set up a
>> cron job to do it, and I haven't even tried getting it to email me a
>> daily summary.
>
> HA can be installed in several ways.
I had no idea why I chose Domoticz over HA, it was a few years ago, but
you present a compelling argument.
My rpi4 Domoticz install is a 12 line docker-compose.yml.
I already had MQTT.
Domoticz works, lets me switch things on and off, immediately or
scheduled, and provides me with historical usage graphs. Which is all I
really want.
Dunno if it relates to you, but I had a similar SSH problem.
I had a Gitea Container (a pretty UI git repo manager) needing to
reserve the standard SSH port for git to work, this took over the host
rPi host standard SHH port. My solution was to assign the Gitea
container its own LAN IP address using a Docker Macvlan network drive,
thus the Gitea container and the host rPI could each use the default SSH
port as they had distinct IPs.
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
