I’ve switched from HA Supervised with some daemons running on Debian that monitor the syslog and act upon some entries that appear - to HAOS running on a VM. What is the best way to tail the syslog within HAOS (or journactl as appropriate) to act upon the entries where they are now appearing?
Hello KruseLuds,
This is out there. Haven’t used it but maybe.
Also I pulled this search string in a search engine, there may be more info there if you dig.
site:home-assistant.io syslog
Thank you @Sir_Goodenough - looking into this right away!
Update: Actually as my HAOS is on a VM it’s a little different, there are two logs involved, the logging within the VM vs. logging on the host!. Also evidently within that VM (QEMU) the CPU temp is unavailable anyway - and I don’t want to put any other processes on that host - so to kill two birds with one stone I actually have daemons on a second physical machine, making calls to the first machine to retrieve the CPU temp and tail it’s host syslog remotely and well as other information from outside of HAOS on both machines, then that second machine calls the HA rest API on the first machine to populate & update the sensors needed within HA in a timely manner. It works very well, the only hiccup I ran into was that I had to add some error handling to be able to every 30 seconds or so continue attempting a reconnection on the fly - if the connection between the two machines is lost for whatever reason or if either or both are being rebooted.
1 Like