Posts made by digied

@wishmaster270 I did some research. Somehow the network wasn’t right anymore. The cam got a different ip-address, so it was rebooted somehow and using DHCP got a different address. Now it is set to the same address. I did replace the first switch to which the NAS and the cam are connected. For the cam I use a repeater that uses the electrical net to connect to my backbone. A cable would have been difficult. After a reset of all that components, the cam was reconnected and all is working again.

@wishmaster270 No, the cam has died. Need to buy a new one.

@wishmaster270 Suddenly, starting today, I see the grey square with the little cam in it. Didn’t change a thing!

Log:
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: kan gedeeld objectbestand niet openen: Toegang geweigerd (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: kan gedeeld objectbestand niet openen: Toegang geweigerd (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21.02.2023 17:25.05.039] [LOG] MMM-SynologySurveillance: Received notification CONFIG
[21.02.2023 17:25.05.040] [LOG] MMM-SynologySurveillance: Received notification INIT_DS
[21.02.2023 17:25.05.042] [LOG] MMM-SynologySurveillance: Updating information of DS with idx: 0 and protocol https
[21.02.2023 17:25.07.730] [LOG] MMM-SynologySurveillance: Problem during fetch of cams of ds with idx: 0
[21.02.2023 17:25.07.730] [LOG] MMM-SynologySurveillance: {
“errno”: -3008,
“code”: “ENOTFOUND”,
“syscall”: “getaddrinfo”,
“hostname”: “datanas”
}
[21.02.2023 17:25.07.731] [LOG] Unknown error. Sending empty list of streams!
[6591:0221/172507.750557:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!

Can I do anything?

@wishmaster270 Installed the update and all is working fine now. Thanks for your help. :folded_hands_light_skin_tone:

@wishmaster270 said in MMM-SynologySurveillance:

.MMM-SynologySurveillance .cam {
  width: 100%;
}

Yes, together with height: 100% as well the image is there. Thanks!

@wishmaster270 Sorry, haven’t seen your change of the replaceHostname before. I now set it to false and now I can see the image, but very small at the moment. SO the stream is working now, I just have to get the image larger now. Thanks for your help!

@wishmaster270 Great! I did see the certificate error so I changed the https/5001 into http/5000 in the config and now the log shows this:

[16.01.2023 20:49.14.962] [LOG] MMM-SynologySurveillance: {
“dsIdx”: 0,
“camStreams”: {
“Generic_ONVIF-001”: “http://datanas//192.168.2.26:5000/webapi/entry.cgi?api=SYNO.SurveillanceStation.Stream.VideoStreaming&version=1&method=Stream&format=mjpeg&cameraId=2&StmKey="6058a182182e0c518d126bbf69e2e350"”
}
}
[73749:0116/204923.065357:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[73749:0116/204930.176714:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[73749:0116/204930.183104:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[16.01.2023 20:50.05.716] [LOG] MMM-SynologySurveillance: Received notification REFRESH_URLS
[16.01.2023 20:50.05.718] [LOG] MMM-SynologySurveillance: Refreshing the urls!
[16.01.2023 20:50.05.719] [LOG] MMM-SynologySurveillance: Updating information of DS with idx: 0 and protocol http
[16.01.2023 20:50.08.721] [LOG] MMM-SynologySurveillance: Found cam Generic_ONVIF-001
[16.01.2023 20:50.09.721] [LOG] MMM-SynologySurveillance: {
“dsIdx”: 0,
“camStreams”: {
“Generic_ONVIF-001”: “http://datanas//192.168.2.26:5000/webapi/entry.cgi?api=SYNO.SurveillanceStation.Stream.VideoStreaming&version=1&method=Stream&format=mjpeg&cameraId=2&StmKey="6058a182182e0c518d126bbf69e2e350"”
}
}

Now the certificate error is gone, but still no image from the cam.

@sdetweil Sorry…

@wishmaster270 I see that my previous post wasn’t published. So I repeat it; I deleted the MMM-SynologySurveillance map and did the git clone again. This time I see the line syno:latest. So I did the npm install without the sudo and restarted MM. Now instead of the grey square with the cam, I get a grey square with some little square in it like this:

So now what?

@wishmaster270 I changed nothing. I only fetched the module again as you can see. The latest module is now installed with npm install. So no sudo this time. Now what?