[Support]: hailo not working #18313
Unanswered
34t614t1254y
asked this question in
Detector Support
[Support]: hailo not working
#18313
Replies: 4 comments 11 replies
-
|
you'll need to run the command there to get the information, this error occurred in the hailo driver |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Thank you for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
looks like an issue with the driver or hardware, at this point you'll likely need to get support on the hailo forum as I am not familiar with these errors. Have you tried a full system restart to see if it continues? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that's correct. |
Beta Was this translation helpful? Give feedback.
-
|
Seems like it might be a power issue, the demand is too high when running for multiple cameras |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I literally just started setting up the AI HAT+ on A raspberry Pi5, and came across the same issue. However I don't appear to be seeing the same messages about Details as below. Version0.16.0-beta2 In which browser(s) are you experiencing the issue with?Microsoft Edge 136.0.3240.76 (64) Frigate config filedocker-compose file or Docker CLI command
Relevant Frigate log outputRelevant go2rtc log output
Operating systemHome Assistant OS Install methodHome Assistant Add-on Network connectionWired Camera make and modelHikvision DS-2CD1383G2-LIUF/SL Screenshots of the Frigate UI's System metrics pagesnone Any other information that may be helpfulOutput from |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Also from this link https://community.hailo.ai/t/fresh-setup-having-issues-with-failed-written-bin-files/13042 it seems that |
Beta Was this translation helpful? Give feedback.
-
|
So as of about 20 minutes ago I got it to work. There were 2 things that I did. Firstly I built the 4.20.1 hailort firmware from the release zip on pi os, and on, reboot i could see the firmware loaded to the chip. At this point frigate was still throwing the same error. Secondly I tried using the standard frigate beta rather than the full access version. It was at this point that it came up. Hopefully @34t614t1254y you're also using the fa version, and switching will sort it, but if not try doing what I did with the firmware. @NickM-27 I'm not sure of the differences between the standard and full-access beta versions are, but if that fixes it for us both it might be worth investigating. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@NickM-27 was trying a few things this morning around hardware acceleration, and decided to try the 0.16.0-beta4 fa version of the addon. Turns out that it can't connect to the hailo device unless protection mode is disabled. |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
That's not something to fix, that's required when you run the full access version |
Beta Was this translation helpful? Give feedback.
-
|
Hi @NickM-27 it's definitely required in order to make the fa version work in hassos on a rpi5. I'm not sure what the issue is, but it's the only way I could get it to work. |
Beta Was this translation helpful? Give feedback.
-
|
When you run full access, you have to disable it so it has access to the hardware. In most cases the default addon can be used instead of full access |
Beta Was this translation helpful? Give feedback.
-
|
I absolutely agree @NickM-27 however the docs clearly say that the fa version is "Current release with the option to disable protection mode". It doesn't say anywhere, that this is required. Nothing major, but will definitely help with tickets like these! |
Beta Was this translation helpful? Give feedback.
-
|
My confusion was coming from the fact that I was running full access before with coralTPU USB and didn't need to disable the protection. Thanks for the clarification! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
I am using the Frigate beta version, downloaded on Home Assistant OS.
After installation, I edit the config.yaml file, and it runs successfully.
However, after rebooting the device, an error appears, as shown in the logs below, and it doesn't work.
If there are many cameras, the device doesn't boot at all.
The device I'm using is a Raspberry Pi 5 with a Hailo-8L module attached, and it's running from an SSD. (This is a standalone Home Assistant installation, not virtualized).
Steps to reproduce
Version
0.16.0-beta2
In which browser(s) are you experiencing the issue with?
Microsoft Edge 136.0.3240.76 (64)
Frigate config file
docker-compose file or Docker CLI command
noneRelevant Frigate log output
Relevant go2rtc log output
Operating system
Home Assistant OS
Install method
Home Assistant Add-on
Network connection
Wired
Camera make and model
Reolink RLN8-410 NVR
Screenshots of the Frigate UI's System metrics pages
none
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions