EDIT: Tried on a second similar install, which includes a number of addons including a non-running Motioneye.
Will try tomorrow with a fresh supervised install and report back.
Just a brief dig, it looks like some packages had revisions. If you can access the docker build script, these packages need to be updated to these versions.
Great work @Bigrob8181. I have been using Shinobi for some time, firstly with Docker, but more recently as a standalone install on an Ubuntu VM.
IMO, itâs far better than MotionEye, especially if you are running your HA instance on lower end hardware or an SBC. Shinobi uses less RAM, less CPU, file saves are smaller, itâs just better all round.
Well done on reviving this, and I hope more people start using it.
This resulted in no errors, but the installation gets stuck with a spinning wheel. Checking Portainer there is a random-named container that is running, but nothing available at :7440.
Retrying shortly with more logging turned on.
EDIT: After reboot the container is still there, and now I can access the config âtabâ of the addon.
When I click Start, I get a spin and it goes back to Start.
Log shows:
20-06-03 16:36:53 ERROR (MainThread) [supervisor.utils] Canât execute run while a task is in progress
So for the time being, since I have no where near the expertise to troubleshoot this, Iâm using a separate container with Shinobi installed. CPU usage is so low compared to Motioneye!
Hopefully the addon can be sorted as that would be my preferred method.
@Hurricane,
I have updated the code in the repo and have verified it to work on my intel nuc. I also updated the shinobi verson to latest commit as of today.
I was able to install the addon! Realized that I needed MariaDB so I installed it as well.â
I tried on my Raspberry Pi OS build (where I want to use it) and my NUC build as well, with the same result.
I am unable to start it though, and the container log shows:
[s6-init] making user provided files available at /var/run/s6/etcâŚexited 0.
[s6-init] ensuring user provided files have correct permsâŚexited 0.
[fix-attrs.d] applying ownership & permissions fixesâŚ
[fix-attrs.d] done.
[cont-init.d] executing container initialization scriptsâŚ
[cont-init.d] 10-requirements.sh: executing⌠[23:08:25] FATAL: The configured certfile is not found
[cont-init.d] 10-requirements.sh: exited 1.
[cont-finish.d] executing container finish scriptsâŚ
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Try removing âssl: falseâ from the config. Looks like I might have made a mistake in the logic for a lot of the config options. I will test and update possibly tomorrow.
@Hurricane,
I just updated the logic. I think this should fix it for you. Give it a shot. To answer your question, i have not used motion detection, i just enabled it, seems to work.
@dcjona,
How are you trying to add the repo and what url are you using?
I found the issue again. This time, it is due to updating shinobi to yesterdays commit in which the motion conf is no longer required as of this commit. I havent dug too deep into the motion changes.
This should get you all of the way. Let me know how it goes.
hi @Bigrob8181, thanks for maintaining Shinobi for HASS. I wanted to give this a try because Motioneye seems a bit resource intensive. I was able to add your repository to my setup, but am unable to get it loaded. I have MariaDB running, with a separate DB for shinobi.
My error messages are as follows. Any ideas what is wrong? Thanks in advance.
No âffbinariesâ. Continuing.
Run ânpm install ffbinariesâ to get this static FFmpeg downloader.
No âffmpeg-staticâ.
Available Hardware Acceleration Methods : vdpau, vaapi
FFmpeg version : 4.2.1
Node.js version : v12.15.0
Shinobi : Web Server Listening on 80
2020-06-09T11:04:06-06:00 Current Version : e16832faad32fe27e8598f1d303dbb9617d35738
I tried your latest commit, and had it install the ffbinaries. I found it to be far more CPU and RAM intensive by approximately double, with no discernible increase in quality or speed. I did notice that the log no longer listed any hardware acceleration and Iâm thinking that is a least part of the issue.
Reinstalling without the ffbinaries works really well.