Read the statement by Michael Teeuw here.
MMM-SynologySurveillance
-
@digied Just released a new version which fixes the host part replacement
-
@wishmaster270 Installed the update and all is working fine now. Thanks for your help. :folded_hands_light_skin_tone:
-
@digied Great to hear that. You are welcome.
-
@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?
-
@digied Hi,
looks like a DNS problem to me. Your Mirror can not resolv the ip of “datanas”.
Did there happen a update of your router maybe?
-
@wishmaster270 No, the cam has died. Need to buy a new one.
-
@digied
Oh, did not expect a dead cam resulting in this error message.
Especially as at this point all cams configured in the NAS are fetched. -
@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.
-
Hi. I love Your module.
Do You know if there is a way to get better resolution than width of 320px?
I mention width only since I have one 4/3 cam and 3 reolink duo which is 8/3.
For all of it, best quality I can get is 320/xxx.By many experiments I have found that this is best I can get and enlarging it with method you posted will drop in quality.
I think it can be somewhere in DSP configuration but can not find it at all…
BTW. none of my cameras provide mjpeg stream but can provide jpeg snapshots. Maybe it is worth to implement this solution as well…
-
@m3iaz Hi,
the Reolink cams provide a fluent and a high quality stream.
You can select three different stream types in the Surveillance Station. The MJPEG stream is generated of the one for reduced speed which in my setup is the fluent stream of the Reolink cam.
I can select a 640x stream in my Reolink but it may depend of the camera.I do not have much time to program at the moment but you may checkout my EmbedURL module. It is able to embed images and a refresh rate can be configured. Some people use it to embed JPEG of public webcams already.
