MichaIng
commented
5 months ago Please report this to the Home Assistant core bug tracker: https://github.com/home-assistant/core/issues We are not related to his HA integration, and AFAIK it is still based on the old motionEye 0.42.1 codebase (which makes sense, since we did no 0.43.x release yet).
But some hints for investigation to take over:
- It is possible that camera/ffmpeg processing heavily utilises the RPi 4 CPU, especially with multiple cameras, like in your case, and/or when no hardware acceleration is possible.
- Since you use HA supervised (?), I am not sure which camera backend is used, which libraries available, which GPU features enabled on the RPi etc. So it makes sense to check whether hardware acceleration for FFmpeg is done or not, and in case change things for it to be done.
- And of course, any CPU load must not crash the RPi 4: Check CPU temperatures and for power/voltage warnings:
vcgencmd measure_temp # in case you have RPi OS as host system dmesg -l 0,1,2,3 - Also check RAM usage:
free -h
After installing MotionEye ver 0.20.0 on my RPI 4b which has been working perfectly for over 2 years now I started to get issues, initially it looked like the LAN port might be faulty but it was then when I added another USB camera I was losing my RPI 4b multiple times a day off the network I checked CPU and memory which was hovering normally at around 50% usage but I was losing the RPI 4b at least once every 45 - 60 minutes for the reboot time of 3 minutes so I don't know if motioneye reached a point where it maxxed out the RPI and it just gave up and rebooted.
After spending a whole day going through things I unplugged the USB cameras, checked the RPI PSU was ok and made sure that no other hardware was causing this issue I found that by removing the Add on from HA the RPI reverted back to normal behaviours. I was not able to find ANY logs recording the issues since the RPI just randomly kept restarting.
Home Assistant Core 2024.5.5 Supervisor 2024.05.1 Operating System 12.3 Frontend 20240501.1