Regarding the kernel messages: I’ve successfully reproduced these on my end and have opened a ticket with the team. We’re working on a fix that should be included in the next release. It would be helpful if you could let me know if these messages appear when using something other than Frigate. I’ll update you once this is resolved.
Regarding the command warning: hailortcli run2 is actually the correct approach for HailoRT 4.23 and version 5+. I understand the warning message is confusing – we maintained the run command for API compatibility, but the warning itself is actually a bug. I’ve escalated this to R&D to have it corrected.
Regarding the version 4.23 files: You’re correct that the Frigate developer doesn’t host those files, but this is easily addressed. Here are the direct links to the required files:
For Hailo-8:
x86_64/amd64:
- HailoRT: http://dev-public.hailo.ai/2025_10/Hailo8/hailort_4.23.0_amd64.deb
- Python Wheel: http://dev-public.hailo.ai/2025_10/Hailo8/hailort-4.23.0-{PY_TAG}-linux_x86_64.whl
aarch64/arm64:
- HailoRT: http://dev-public.hailo.ai/2025_10/Hailo8/hailort_4.23.0_arm64.deb
- Python Wheel: http://dev-public.hailo.ai/2025_10/Hailo8/hailort-4.23.0-{PY_TAG}-linux_aarch64.whl
(Replace {PY_TAG} with your Python version: cp310-cp310, cp311-cp311, cp312-cp312, or cp313-cp313)