Synology Surveillance Station Binding

Add-on Marketplace Bundles
, ,
61

I don’t understand your setup fully. I have one Station, one camera and one password.
So I create a bridge:
synologysurveillancestation:station:c3ee28d7f4
and the Thing is found:
synologysurveillancestation:camera:c3ee28d7f4:2
Note, it’s one Station and one Camera with the same Station serial and its id (2) behind.

In your log I see no Station but three Cameras with the same Station serial.
Are those different Cameras or have you just reinstalled the Binding?
In any case, if you actually have three sets of credentials, only the camera with proper credentials would probably work then. Multiple Stations (Bridge) may work as well.
I also see you’ve got at least one proper call through, so you might be already almost there.
If you wish, you can PM me with a fuller log (and in German if desired), as not to clutter the forum.

62

Same here.
I have one station and one camera.
But before I could use the camera in the station I first had to set it up with it’s own user and password.
The station itself has its own users and passwords as you know.

You are right. I have reinstalled the whole setup a couple of times. I thought I did something wrong in the first place.

63

I see you’ve updated your log and it seems to run as expected. Is your issue solved then?

64

Unfortunately no.

I create a thing to the bridge:
synologysurveillancestation:station:b3d6866041 (account)
No camera found automatically

Then I create a camera-thing to the bridge:
synologysurveillancestation:camera:b3d6866041:f1d250ad6a (use the suggested UID)

Then I create an item to use camera-things channels → Camera is offline.

Actually everything seems very simple. But somehow it doesn’t work :frowning:

65

Maybe I’m the only one, using a TC500 via Suveillance Station in openhab :crazy_face:

66

Strange… could you please recreate your Camera Thing either with ID 1 or 2 instead of f1d250ad6a:
synologysurveillancestation:camera:b3d6866041:2

67

I did that already after I have read your message. The result remains the same.

68

Do you know, how Green93 solved his problem. Maybe his would be the needed hint to the solution.

69

No, I hope he had… :confused:
@Green93 are you around? :slight_smile:

Have you already tried the ssl bypass option as suggested in the log? (OH restart might be needed)
You could also try to paste the first link from your log
http://192.168.14.5:5000/webapi/entry.cgi?api=SYNO.SurveillanceStation.Camera&version=8&method=List…
in any browser, perhaps there is some additional output…

70

I’ll try and come back to you.
Bit first I go and have a beer now. I have one for you as well.

71

I’m on it already :stuck_out_tongue:

72

Hi Pavion,

your hint with checking the link put me on the right path.
The default IP address (5000) was not correct. I couldn’t figure it out because the binding thing always said ‘online’.
I entered a new port for the Surveillance Station in the DSM under applications and now everything works :slight_smile: Just so simple. Thank you for your great help. Maybe the beer helped a little too :wink:

1 Like
73

Hi Pavion,

Unfortunately, I still have a question. I’ve tried for a long time before, because I don’t want to annoy you too much, but I can’t get anywhere.
How is an intruder alarm triggered by the station in openhab?
Only the following entry is made in the event log every 3 seconds:

RESPONSE: {"data":{"events":[],"offset":0,"timestamp":"1710088518","total":0},"success":true}

Is that even possible?

Greeting
Markeese

74

Hi there, also unfortunately I can’t give you a direct answer.

I don’t know what is an intruder alarm. There are six event channels in this binding, they should be linked first or you won’t see them in the above API response. If your event is not triggering you might be able to make a workaround by creating a Surv.Station rule, which would then trigger a custom event.

Well… It might also be broken altogether. It’s years since I’ve tested it last time and the used API is deprecated since many years.

If you can’t reach your goal with tips above and are really needing it, with your help and some additional info I might look into it again.

BR
Pav

75

Just upgraded my Synology DS1815 to the latest version of Survalence Station 9.2.0-11289.

I now see errors in the logs for all cameras I have set up in Openhab3.

2024-04-06 14:18:23.738 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:25.796 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:33.152 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:35.250 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:43.685 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:45.905 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}
2024-04-06 14:18:51.730 [ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {"error":{"code":105,"errors":{"param1":"","param2":""}},"success":false}

This error did not occur before the upgrade, so I think it is specific to the NAS’s new version of the Survalence Station software. It has nothing to do with the Openhab setup, as it worked perfectly before the NAS upgrade.

The Openhab version I am running on my RPi4 is 4.1.2

I do note when I look at the Openhab3 admin page for the Binding (http://192.168.1.98:8080/settings/things/synologysurveillancestation:station:1810mhn315000), I see the online status cycle between online and then offline. This cycle matches the errors in the logs. I have tried rebooting the NAS, but no change.

Is this a new issue? I’m keen to see if anyone knows how to resolve this. Any help would be greatly appreciated.

Cheers

Ian

76

Hi Ian! According to the API, error 105 is: Insufficient user privilege.
You might need to check your credentials or to create a dedicated Surveillance Station user.
Your IP could also have been blacklisted by the DSM, so you might need to clear its blacklist first.

77

Thanks @Pavion , Much appreciated.

It is interesting because the Binding was showing ‘online’, and I was obtaining the snapshots from the camera ‘thing’. The ‘thing’ was mostly online, but every few seconds, it would go offline and then online again. Each time it goes ‘offline,’ I get the log entry with the param1 and param2 messages.

I now have a different issue, as the Synology account is forcing 2FA, and I cannot see a way to enter this via the Openhab Binding. Any help would be greatly appreciated.

I think I have gone backwards, not forwards, on this issue!! :wink:

Hoping you can help

Cheers Ian

78

There might besome performance issues regarding Raspberry, if the signal flackers, you should try to increase the timeout.
As for 2FA, it is not supported, but you should be able to create a dedicated viewonly user in Surv.Station.

79

Thank you @Pavion

That worked.

Oddly enough I needed to enable 2FA (by logging into the NAS from the browser and following the 2FA setup), then log back in as Admin and disable 2FA via the User & Group in Control Panel on the NAS.

Once I did that I disabled then enabled the Binding.

No errors, and so far, all seems good.

Thank you again for all your help.

1 Like
80

What exactly did you do?
I have the same error and Things going offline:

[ERROR] [ternal.webapi.request.SynoApiRequest] - RESPONSE: {“error”:{“code”:105,“errors”:{“param1”:“”,“param2”:“”}},“success”:false}

I already have a separate user and no 2FA activated. I changed the password as well, but the error remains. It’s also updating the snapshot items properly. I believe this is since the Surveillance Station got updated.