frigate-hass-addons: New rknn detector not working on home assistant add on.

Description

I can`t start the add on on 13 beta-6 version when testing the new rknn detector. I am using an orangepi 5 with a Rockchip RK3588S. But i gives the following error when starting.

image

The file does exists from a ssh connection to the orangepi, but i don`t know if is really a bug or i am missing any configuration to make the docker container access this file (I already disabled protection mode).

image

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Comments: 81 (12 by maintainers)

Most upvoted comments

For everyone who wants to use HA and frigate for rockchip:

Currently, there is only one way (Home Assistant Container): Install a distro that has all necessary drivers (I recommend this one, if you have a rk3588/s soc) and install docker. Then use the HA docker image (see here for install instructions and here for instructions to migrate your data from a previous HAOS installation) and install frigate separately using docker. However, this will be very annoying for people who use addons a lot, because you will need to setup all addons separately using docker. See here for differences between HAOS and HA Container.

In the near there will be (hopefully) another way to use HA and frigate together on rockchip boards (Home Assistant Supervised): Once again install a distro that comes with all drivers and follow the instructions to install HA supervised. Then install the frigate-rockchip addon. As one can see here, HAOS and HA Supervisor offer similar features. Most notably, you can install addons using this method. Migration from previous HAOS install should also be easier using the Backup function. People who want to have an experience similar to HAOS should wait until this method works. However, this will probably take some weeks, because the HA teams needs to implement a feature to allow the addon to mount the device-tree to another path. I tried to contact one of the devs about this feature request, but he didn’t respond so far.

The best way is of course to use HAOS directly. However, this will take at least 1+ year, because the Collabora team (or other contributors) needs to develop a rkvdec2 and rknpu driver, merge them into the mainline kernel repo and HAOS needs to use this kernel (it usually doesn’t use brand new kernels but rather older/ more stable kernels, so it lacks some months behind new features).

Привет @Ra3eR63 , Проверки что написал MarcA711 надо сделать из контейнера, вставьте в терминале :~# docker ps , найдите CONTAINER ID фригата , затем в терминале выполните: docker exec -it ********* /bin/bash , вместо звездочек CONTAINER ID, вы попадете в контейнер фригата и там выполните : ls /dev/dri , и cat /sys/kernel/debug/rknpu/version

@pedrol3001 you can try this as well by the way, just need to run docker exec -it ccab4aaf-frigate-rk-beta /bin/bash to get a shell