HASS Addon Shinobi [Revival]

Thanks for reviving this addon. I use blue iris now, but my machine isn’t greatly specced and the forced windows updates keep getting messed up and taking down my NVR.
So I’m looking at ways to keep an NVR without having to run it on windows.

This was a super easy way to get shinobi running for a test drive.

Thanks @Bigrob8181 for reviving this addon.

Any idea why it was discontinued by @frenck ?
Are there plans to make it back to the community addons ?

thanks
-a

Few other questions if somebody can chip in

  1. Any guide to automatically handle the ssl certs in case of working with ngnix proxy manager? I believe without those certs and ssl: true, one cannot add it in ipanel.

  2. how to pass/provide a different fs drive for recordings?
    Context: having HA Supervised where one ssd is used for OS, and a hdd drive for shinobi recordings.

Thanks
-a

Thank’s @Bigrob8181 for your effort and time to make this addon available again :+1:

Sadly it isn’t installable anymore with home assistant 0.104.

There is also an issue on github where various people report the problem

Hi, any chance of a fix for the installation issue in HA 0.104+ ?

There’s no need for an add-on if you can deal without triggers and just want to monitor cameras. Shinobi has a great API. See here Shinobi Camera Component

Sorry it has taken so long to get around to fixing. Latest version should address the build issues, and minimize/prevent further issues.

1 Like

@Bigrob8181 Hi!
There is a possibility to add this integration to HACS? I’m using Home Assistant Core …

1 Like

Yeah…will this work in RPi running HA core?

Did you ever find out how to map some different drives for file storage? I’ve got the same situation and my SSD doesn’t have too much capacity left.

I’m taking a leap of faith tagging @Bigrob8181 as well, thanks for a great add-on, I love it!!

But it would come really handy if any other storage could be used. There are capabilities to mount secondary drives to Hassos (https://gist.github.com/eklex/c5fac345de5be9d9bc420510617c86b5) so, if I just could figure out how this works in the add-on the rest is solved.

@Abertil Unfortunately i stopped using shinobi because it was not stable enough in my setup.
Every few days some cameras randomly would stop receive any feed, and addon restart was required.
so i gave up shinobi and went with motion eye, saving on a samba shared network location, and while less customizable and less pretty, at least it’s much more stable.

1 Like

Hi

i installed it today. but no success. i get this error in the log and i can t log in:

FFmpeg version : 3.4-static http://johnvansickle.com/ffmpeg/
Node.js version : v12.18.4
Shinobi : Web Server Listening on 80
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This Install of Shinobi is NOT Activated
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2020-12-28T22:09:06+01:00 This Install of Shinobi is NOT Activated  
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
https://licenses.shinobi.video/subscribe
2020-12-28T22:09:06+01:00 Shinobi is ready.  
knexError----------------------------------- START
[Error: select * from `Schedules` - SQLITE_ERROR: no such table: Schedules] {
  errno: 1,
  code: 'SQLITE_ERROR'
}
select * from `Schedules`
knexError----------------------------------- END
Uncaught Exception occured!
TypeError: Cannot read property 'forEach' of undefined
    at /opt/shinobi/libs/scheduler.js:11:18
    at /opt/shinobi/libs/sql.js:186:33
    at cb (util.js:207:31)
    at util.js:191:10
    at hidden (internal/errors.js:291:14)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

what can i do to fix it?

Did you install and configure MariaDB properly as well? Looking at the error, that is my guess.

Hi, this is my Maria-DB Config

databases:
  - homeassistant
  - shinobi
logins:
  - username: homeassistant
    password: homeassistant
  - username: shinobi
    password: sh1n0b1
rights:
  - username: homeassistant
    database: homeassistant
  - username: shinobi
    database: shinobi

i think it is correct?

Looks about the same as I have, I’ve also got a few lines for grants, but I’m not sure those are needed.

How does your Shinobi config look like?

i m using this config

log_level: info
super_username: [email protected]
super_password: admin
mysql: false
mysql_host: core-mariadb
mysql_username: shinobi
mysql_password: sh1n0b1
mysql_database: shinobi
mysql_port: 3306
mail_service: gmail
mail_username: [email protected]
mail_password: maypassword
mail_host: smtp.gmail.com
mail_port: 587
mail_secure: false
mail_cert_verify: true
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
ffbinaries: false

Try to change myql: to true, I think that will solve it.

Hi

no the Log looks better. But i can t log in. if i try to login with this:

super_username: [email protected]
super_password: admin

nothing happens

this is the log:

[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... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 20-init-configuration.sh: executing... 
[cont-init.d] 20-init-configuration.sh: exited 0.
[cont-init.d] 21-symlink-configuration.sh: executing... 
[cont-init.d] 21-symlink-configuration.sh: exited 0.
[cont-init.d] 30-superuser.sh: executing... 
[cont-init.d] 30-superuser.sh: exited 0.
[cont-init.d] 31-mail.sh: executing... 
[cont-init.d] 31-mail.sh: exited 0.
[cont-init.d] 32-db.sh: executing... 
[cont-init.d] 32-db.sh: exited 0.
[cont-init.d] 33-ssl.sh: executing... 
[cont-init.d] 33-ssl.sh: exited 0.
[cont-init.d] 40-mysql.sh: executing... 
[cont-init.d] 40-mysql.sh: exited 0.
[cont-init.d] 50-ffbinaries.sh: executing... 
[20:08:32] INFO: Installing ffbinaries...
[cont-init.d] 50-ffbinaries.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Change your cron key in your conf.json.                     !!
!! If you're running Shinobi remotely you should do this now.  !!
!! You can do this in the Super User panel or from terminal.   !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ffbinaries : Downloading FFmpeg. Please Wait...
ffbinaries : FFmpeg Downloaded.
Available Hardware Acceleration Methods :  
FFmpeg version : 3.4-static http://johnvansickle.com/ffmpeg/
Node.js version : v12.18.4
Shinobi : Web Server Listening on 80
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This Install of Shinobi is NOT Activated
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2020-12-30T21:09:54+01:00 This Install of Shinobi is NOT Activated  
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
https://licenses.shinobi.video/subscribe
2020-12-30T21:09:54+01:00 Shinobi is ready. 

Ok, what are you trying to login to?

You have a few choices and the only choice that will work with the credentials that you are using is the super login. I.e at the url http://ip:port/super

ok. found it.

http://192.168.1.180:7440/super