Cannot Connect to Shinobi - Missing Permanent API Key about ha-shinobi HOT 13 CLOSED

Please check issue #39 and let me know if the workaround works for you

Thanks

from ha-shinobi.

I assume you are referring to:
The workaround is to set value in the NVR or wait for next release, hopefully tomorrow

I already had the number of days of video to retain set to 28 in Shinobi. This did not work.
Please advise if there is something else I should be checking/setting.

from ha-shinobi.

I had it on Saturday but it was related to Shinobi, didn't see the key over the UI of Shinobi although it was available over the API, redployed it and it started working again,
If that does solve the issue i will need to investigate in logs and maybe release an additional release with more logs

from ha-shinobi.

Having the error in line 203 makes me wonder if you are using the latest version or did it took place when you have restarted the HA

from ha-shinobi.

from ha-shinobi.

Shinobi has many latest versions, which branch?

from ha-shinobi.

checked about that issue, not sure whether it's the same issue I have expirenced last Saterday or another one as described in
released a new version v2.0.28 with potential workaround / fix for the issue foudn while working with aiohttp, more details available here

from ha-shinobi.

@algaen pls let me know if it solved the issue, thanks

from ha-shinobi.

Shinobi has many latest versions, which branch?

This is slightly embarrassing but I cannot tell. When I log in to 'Super' the current version number is blank. I also checked the logs but it does not list the version number.

That said, I am running the SpaceInvaderOne 'ShinobiPro' docker installed on Unraid from Community Applications. It has not been updated in 10 months. I typically update my containers in bulk so just assumed it was getting regular updates. Thanks for asking the question as it made me realize I may not be using the correct docker container.

Before pursuing further troubleshooting let me test with another Shinobi docker that is more up-to-date. I hope to do that tomorrow evening.

from ha-shinobi.

checked about that issue, not sure whether it's the same issue I have expirenced last Saterday or another one as described in released a new version v2.0.28 with potential workaround / fix for the issue foudn while working with aiohttp, more details available here

I updated to v2.0.28 tonight but it did not resolve my issue - same error. See my previous comment. I will try an updated version of the Shinobi docker container tomorrow.

from ha-shinobi.

If that didn't solve the issue it basically means that the problem is with the ability of the server to get requests,
Not sure what build your server is based on, for sure it is not the official one and therefore I cannot assist,
Making a single request to the server for specific endpoint is not what that integration is doing (query several endpoints on load / updat,
Can you pls switch to the official docker (preferably dev tag)?

from ha-shinobi.

If that didn't solve the issue it basically means that the problem is with the ability of the server to get requests, Not sure what build your server is based on, for sure it is not the official one and therefore I cannot assist, Making a single request to the server for specific endpoint is not what that integration is doing (query several endpoints on load / updat, Can you pls switch to the official docker (preferably dev tag)?

Upgrading to the official docker appears to have solved my problem. Thank you for the support!

from ha-shinobi.

Thanks for the update, glad to hear it solved the issue

from ha-shinobi.