On Openhab, I deactivated each of my Camera ‘Things’. I left the NAS ‘Thing’ active.
I created a new user on the NAS (Control Panel - User & Group)
Under ‘User Groups’, I selected ‘HTTP’ and ‘users’
Under ‘Permissions’ I selected ‘homes’ as ‘Read/Write’ and ‘surveillance’ as ‘Read only’
Under ‘Applications’ only ‘Surveillance Station’ as ‘Allow’
Once that was set, I tried the new user on the Openhab Thing, and I got a bunch of errors relating to 2FA not being set or something like that.
I then logged in to the NAS via a Browser using the new user ID, and the UI forced me to set up 2FA. This I did.
I tried Openhab again, and as expected, the same errors (at least I think they were the same).
On the NAS, I went back to the Control Panel and User & Group and selected the user. Then, there was an option to disable 2FA, which I selected. 2FA is now disabled.
I then went back to Openhab and deactivated and activated the Thing, and it went online and stayed online. I followed this by activating each of my camera ‘Things,’ and they all went online without any errors.
This is not a complete process, as there are many things that should be tested and ruled in or out, but it worked for me. I am on Openahb version 4.1.2, which I only upgraded to while I was diagnosing this issue. I am not sure if that had anything to do with the issue. I doubt it, but I am sharing it with you just in case.
I tried pretty much the same, but without activating 2FA.
I turned the Things offline, created a new user with the permissions (user & http; homes->default & surveilance->readonly; Apps: DSM, Surveillance Station).
I logged in with that user and verified the password, used the same for the Surveillance Station Thing and I still get error 105.
I first tried to restart only the binding, but that didn’t help, hence I restart openhab and that didn’t help as well.
If I put in a wrong password, I get error 400 instead if 105 and then the Snapshots won’t update.
I also noticed that this problem persists only for my Reolink and Annke Cams. There is an AXIS P1355 Cam that I use for my 3D Printer, that works just fine. I even set the refresh rate on that one to 5 seconds (usually 60s) without issues. The only difference I can see that could matter is the resolution being only 1920x1080 instead of 2304x1296 (Reolink) and 2592x194 (Annke). However even if I change the Stream Resolution to 1280x720 the error persists.
I also tried disabling and enabling Cams in the Surveillance Station, but without any effect.
When I login with the User into the Surveillance Station I can see successful logins fromt that user, that come from openhab.
I couldn’t find any timeout parameter so set higher. @Pavion any Idea where to configure that?
Long Story short, I found the solution:
As this is related to the new Version of Surveillance Station, I checked the Changelog:
Added support for a new default privilege profile named “Administrator” that grants users access to all objects and the ability to manage Surveillance Station settings. Certain actions that involve modifying DSM settings are restricted and require the user to be added to the DSM administrators group.See all limitations
And that’s it. You need to configure the user as at least Object-Manager. Default seems to be Object-Spectator and that was not enough.
Error Messages are gone immediatly after changing that.
Thanks alot @Piffer , that solves the logs from appearing.
To clarify: You need to set this in the user settings within the Surveillance Station itself.
Hi @Pavion,
unfortunately still no luck with it.
Whenever I create a new channel (either on Camera or Bridge) it says ERROR:COMM thread “Name of the channel”
This is what I get in the link you suggested:
{
"error": {
"code": 103
},
"success": false
}
I also tried to change the default port but nothing changed.
I am having this same error. I’ve been digging into this for a while with no luck. I also just upgraded to 4.3.2 hoping that might help, it did not. The only thing I am currently interested in is home mode. I want to execute some action when entering and exiting home mode. Any suggestions on figuring our the issue?
Hi Scott, please check whether my latest “Release for OH 4.3.0-SNAPSHOT” (at GitHub) works for you. If not, please PM me with some debug output.
BR
Pav
Hey Pav, i got an new issue it seems that i am not receiving motion events, i see they are triggerd on the Synology but the motion item has no changes.
Which infos you need to analyze this problem.
Did motion events work previously with this setup?
If yes, did anything change recently (e.g. DSM update, config changes, OpenHAB version, etc.)?
Unfortunately, I won’t be able to look into it before the weekend, but I’ll check it as soon as I can. In the meantime, any additional details you can share would be helpful.
Hi, thanks for your reply.
belive it or not, after i posted this thread i have received an motion event… i will keep an eve on that again, and nothing changed.
