10 minutes is too long. I don’t want spam every 1-5 seconds, but I also don’t want to wait 10 minutes to be notified of a security issue, as that would be useless. I could set it to 15 seconds, but the question is, how do I use that condition in the add-on “MotionEye”?
I mean, I don’t see how to set a Home Assistant condition in MotionEye’s motion notification settings, and I don’t even think it’s designed for that (but maybe I don’t know how it works) since it’s not configured from Home Assistant but from its own add-on: Motion detection on motioneye - #9 by aceindy
In any case, I’ve already tried the solution proposed by browetd in the link I posted earlier, and now my infinite loop is working for me, writing every 90 seconds to the log as an example, so that solution should work for me. I have to adapt my script because HAOS’s busybox ls does not accept the --time-format command, but that’s not a big deal.
However, running ps -aux does not show me that script and now I don’t know how to kill it. I will look for other ps options or simply check the log.
I suppose you limit HAOS so that we can’t do things like run infinite scripts that overload the CPU/disk or similar things, but I understand that this is everyone’s problem and we use things at our own risk.
In the end, I didn’t have any problems with my scripts in my HA with Docker, I shouldn’t have any with HAOS, and that’s why I don’t quite understand that 60-second limitation. If HAOS launches all user scripts via automations (for example), we should be able to check what is running or not, just like on any other Linux system (and here it’s easier for less experienced users because of the HA interface).