timed out waiting to send media frame

[MicheleCardamone]

Hi! Neolink version 0.5.14 after a few hours of correct functioning, gives the following errors and the video stream does not restore until I close and reopen neolink. I am attaching my config.toml file

config.txt

[0ry0n]

I have the same problem.

[MicheleCardamone]

I have the same problem.

For now i'm using 0.5.11

[apedance]

Same problem here.

[rcastro01]

Same problem here on all my cellular cameras

[QuantumEntangledAndy]

For those that say you have the same issue can you confirm it is for Timed out waiting to send Media Frame there are a few different places where Deadline has elapsed can happen so the additional context is there to help pin down which one is the real issue

[QuantumEntangledAndy]

The issue from what I can see is async exhaustion. Something is not yielding the thread so that means that the buffers aren't being processed and the whole system locks up until timeout happens.

Unless I can replicate and run the tokio-console to visualise locking threads then I won't be able to debug this very well. Is there anything about your setups that might help me duplicate

[kevin-david]

I am seeing this same error during login to 1/2 of my cameras:

[2023-08-04T13:44:46Z INFO  neolink::mqtt::event_cam] backyard_camera: Connecting to camera at Address: 192.168.1.194
[2023-08-04T13:44:46Z INFO  neolink_core::bc_protocol] backyard_camera: Trying TCP discovery
[2023-08-04T13:44:46Z INFO  neolink_core::bc_protocol] backyard_camera: TCP Discovery success at 192.168.1.194:9000
[2023-08-04T13:44:46Z INFO  neolink::mqtt::event_cam] backyard_camera: Logging in
[2023-08-04T13:44:51Z WARN  neolink::mqtt::event_cam] Camera thread error: Failed to login to the camera

    Caused by:
        deadline has elapsed. Restarting...
[2023-08-04T13:47:02Z INFO  neolink::mqtt::event_cam] backyard_camera: Connecting to camera at Address: 192.168.1.194
[2023-08-04T13:47:02Z INFO  neolink_core::bc_protocol] backyard_camera: Trying TCP discovery
[2023-08-04T13:47:02Z INFO  neolink_core::bc_protocol] backyard_camera: TCP Discovery success at 192.168.1.194:9000
[2023-08-04T13:47:02Z INFO  neolink::mqtt::event_cam] backyard_camera: Logging in
[2023-08-04T13:47:07Z WARN  neolink::mqtt::event_cam] Camera thread error: Failed to login to the camera

    Caused by:
        deadline has elapsed. Restarting...

Coincidentally I just upgraded the firmware from Reolink to deal with some RTSP streaming issues with this camera. Wondering if it's related...

[QuantumEntangledAndy]

We are tracking some issue during login that seem to be firmware related in #115

[QuantumEntangledAndy]

Also see #127

[MicheleCardamone]

Also see #127

Hi, the problem: "Timed out waiting to send Media Frame" is solved with 0.5.16?

[skylord123]

Also see #127

Hi, the problem: "Timed out waiting to send Media Frame" is solved with 0.5.16?

Believe this is still an issue. I am on the latest docker release for neolink and still getting this. Only happening on one out of three of my cameras. RLC-423ws is the problem child. The RLC-410 cameras are the other ones that are not having this issue.

Firmware version on camera with issue: v2.0.0.1441_19032113_v1.0.0.30 (last released firmware before being discontinued)

Neolink log:

[2023-08-09T14:00:41Z INFO  neolink_core::bc_protocol] driveway: Trying TCP discovery
[2023-08-09T14:00:41Z INFO  neolink_core::bc_protocol] driveway: TCP Discovery success at 192.168.1.195:9000
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::loggedin] driveway: Camera time is already set: 2023-08-09 8:00:41.0 +06:00:00
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::loggedin] driveway: Camera reports firmware version v2.0.0.1441_19032113_v1.0.0.30
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Main Stream (Clear)
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Sub Stream (Fluent)
[2023-08-09T14:00:41Z INFO  neolink::rtsp] driveway: Buffers prepared
[2023-08-09T18:33:43Z INFO  neolink::rtsp] driveway: Join Pause
[2023-08-09T18:33:43Z WARN  neolink::rtsp] driveway: Retryable error: Timed out waiting for new Media Frame

    Caused by:
        deadline has elapsed

Once I restart neolink the camera feed starts working again.

[MicheleCardamone]

Also see #127

Hi, the problem: "Timed out waiting to send Media Frame" is solved with 0.5.16?

Believe this is still an issue. I am on the latest docker release for neolink and still getting this. Only happening on one out of three of my cameras. RLC-423ws is the problem child. The RLC-410 cameras are the other ones that are not having this issue.

Firmware version on camera with issue: v2.0.0.1441_19032113_v1.0.0.30 (last released firmware before being discontinued)

Neolink log:

[2023-08-09T14:00:41Z INFO  neolink_core::bc_protocol] driveway: Trying TCP discovery
[2023-08-09T14:00:41Z INFO  neolink_core::bc_protocol] driveway: TCP Discovery success at 192.168.1.195:9000
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::loggedin] driveway: Camera time is already set: 2023-08-09 8:00:41.0 +06:00:00
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::loggedin] driveway: Camera reports firmware version v2.0.0.1441_19032113_v1.0.0.30
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Main Stream (Clear)
[2023-08-09T14:00:41Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Sub Stream (Fluent)
[2023-08-09T14:00:41Z INFO  neolink::rtsp] driveway: Buffers prepared
[2023-08-09T18:33:43Z INFO  neolink::rtsp] driveway: Join Pause
[2023-08-09T18:33:43Z WARN  neolink::rtsp] driveway: Retryable error: Timed out waiting for new Media Frame

    Caused by:
        deadline has elapsed

Once I restart neolink the camera feed starts working again.

I confirm, same problem also with 0.5.17

[skylord123]

Actually this seems to happen on the RLC-410 cameras as well. Woke up this morning to 2/3 of the camera feeds broken.

Seems to happen at least once a day to some of my cameras. Reliability isn't great.

[2023-08-15T12:44:17Z INFO  neolink_core::bc_protocol] front_yard_door: Trying TCP discovery
[2023-08-15T12:44:17Z INFO  neolink_core::bc_protocol] front_yard_door: TCP Discovery success at 192.168.1.193:9000
[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera time is already set: 2023-08-15 6:44:17.0 +06:00:00
[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera reports firmware version v2.0.0.843_17061500
[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Sub Stream (Fluent)
[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Main Stream (Clear)
[2023-08-15T12:44:25Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel
[2023-08-15T12:44:25Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 5 (ID: 3)
[2023-08-15T13:52:58Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel
[2023-08-15T13:52:58Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)
[2023-08-15T13:53:08Z INFO  neolink::rtsp] driveway: Join Pause
[2023-08-15T13:53:08Z WARN  neolink::rtsp] driveway: Retryable error: Timed out waiting to send Media Frame

    Caused by:
        deadline has elapsed
[2023-08-15T13:53:08Z INFO  neolink_core::bc_protocol] driveway: Trying TCP discovery
[2023-08-15T13:53:08Z INFO  neolink_core::bc_protocol] driveway: TCP Discovery success at 192.168.1.195:9000
[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::loggedin] driveway: Camera time is already set: 2023-08-15 7:53:08.0 +06:00:00
[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::loggedin] driveway: Camera reports firmware version v2.0.0.1441_19032113_v1.0.0.30
[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Main Stream (Clear)
[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Sub Stream (Fluent)
[2023-08-15T13:53:13Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel
[2023-08-15T13:53:13Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)
[2023-08-15T15:16:56Z INFO  neolink::rtsp] backyard: Join Pause
[2023-08-15T15:16:56Z WARN  neolink::rtsp] backyard: Retryable error: Timed out waiting for new Media Frame

    Caused by:
        deadline has elapsed

[MicheleCardamone]

Actually this seems to happen on the RLC-410 cameras as well. Woke up this morning to 2/3 of the camera feeds broken.

Seems to happen at least once a day to some of my cameras. Reliability isn't great.

[2023-08-15T12:44:17Z INFO  neolink_core::bc_protocol] front_yard_door: Trying TCP discovery

[2023-08-15T12:44:17Z INFO  neolink_core::bc_protocol] front_yard_door: TCP Discovery success at 192.168.1.193:9000

[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera time is already set: 2023-08-15 6:44:17.0 +06:00:00

[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera reports firmware version v2.0.0.843_17061500

[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Sub Stream (Fluent)

[2023-08-15T12:44:17Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Main Stream (Clear)

[2023-08-15T12:44:25Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel

[2023-08-15T12:44:25Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 5 (ID: 3)

[2023-08-15T13:52:58Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel

[2023-08-15T13:52:58Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)

[2023-08-15T13:53:08Z INFO  neolink::rtsp] driveway: Join Pause

[2023-08-15T13:53:08Z WARN  neolink::rtsp] driveway: Retryable error: Timed out waiting to send Media Frame

    Caused by:

        deadline has elapsed

[2023-08-15T13:53:08Z INFO  neolink_core::bc_protocol] driveway: Trying TCP discovery

[2023-08-15T13:53:08Z INFO  neolink_core::bc_protocol] driveway: TCP Discovery success at 192.168.1.195:9000

[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::loggedin] driveway: Camera time is already set: 2023-08-15 7:53:08.0 +06:00:00

[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::loggedin] driveway: Camera reports firmware version v2.0.0.1441_19032113_v1.0.0.30

[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Main Stream (Clear)

[2023-08-15T13:53:08Z INFO  neolink::rtsp::states::streaming] driveway: Starting video stream Sub Stream (Fluent)

[2023-08-15T13:53:13Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel

[2023-08-15T13:53:13Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)

[2023-08-15T15:16:56Z INFO  neolink::rtsp] backyard: Join Pause

[2023-08-15T15:16:56Z WARN  neolink::rtsp] backyard: Retryable error: Timed out waiting for new Media Frame

    Caused by:

        deadline has elapsed

I have same problem but with B800.

The only way to make it work would be to create a task to close and reopen the process automatically after a few hours. For me the problem occurs about every 4 hours. I am currently using version 0.5.11 to run my BlueIris system. Seems to be fine even if about every hour all the cams lose signal for about 2/3 minutes and then restore themselves. Therefore, there still seem to be several problems today, but the developer has stopped responding to this bug of ours. I'm curious to understand if we have this problem only in a few. Mc @QuantumEntangledAndy

[QuantumEntangledAndy]

I have something that might help but your issue might be different from the others as it is to do with async thread exhaustion I think.

I should be releasing it later today so try 0.5.18 and report back after it's out

[MicheleCardamone]

I have something that might help but your issue might be different from the others as it is to do with async thread exhaustion I think.

I should be releasing it later today so try 0.5.18 and report back after it's out

Hi, I tested 0.5.18 but the same problem occurs. I could not see the "timed out" error because the items displayed are different from the previous version. Mc @QuantumEntangledAndy

[QuantumEntangledAndy]

Could you maybe check out this build it contains a few more optimisations that didn't quite make to 0.5.18 that might help.

[MicheleCardamone]

Could you maybe check out this build it contains a few more optimisations that didn't quite make to 0.5.18 that might help.

i can't download it

[MicheleCardamone]

Could you maybe check out this build it contains a few more optimisations that didn't quite make to 0.5.18 that might help.

i can't download it

@QuantumEntangledAndy

[QuantumEntangledAndy]

The links are at the bottom of the page I linked under artifacts. Make sure you are logged in to see them.

[MicheleCardamone]

The links are at the bottom of the page I linked under artifacts. Make sure you are logged in to see them.

hi, Same problem also with this bluid. Mc @QuantumEntangledAndy

[MicheleCardamone]

I don't know how the others manage to make everything work properly, but it seems that even with version 0.5.11 there are constant problems. In 12 hours of operation 12 "no signal" in blueiris.

[skylord123]

Could you maybe check out this build it contains a few more optimisations that didn't quite make to 0.5.18 that might help.

I pulled latest from docker (published 2 days ago) with SHA 75675d782da0 and the problem seems to be resolved for me. No problems for last 30 or so hours. Going to keep monitoring it and will post back if the issue comes back.

[QuantumEntangledAndy]

If you have a chance could anyone test this build got some improvements to hopefully address this, but not sure since I can't replicate well

[QuantumEntangledAndy]

Also for BI please add splash = false as discovered in #114

[MicheleCardamone]

If you have a chance could anyone test this build got some improvements to hopefully address this, but not sure since I can't replicate well

Hi, tested this build with splash = false. Same problem! @QuantumEntangledAndy Config neolink.txt

[skylord123]

If you have a chance could anyone test this build got some improvements to hopefully address this, but not sure since I can't replicate well

So I thought my issue may have been resolved but no its still happening. I noticed there was a new neolink release last night so I upgraded and the cameras stopped working again after a few hours.

Dang, was hoping this was fixed but guess it was just random luck that it worked for so long before the issue came back.

[QuantumEntangledAndy]

@skylord123 What is your error message. The newer builds I expect to show maybe DroppedConnection error rather than the original timed out waiting to send media frame.

I'd like to tackle this one but I need some help finding out how to replicate so if any one could share their camera and setup it would help

[MicheleCardamone]

@skylord123 What is your error message. The newer builds I expect to show maybe DroppedConnection error rather than the original timed out waiting to send media frame.

I'd like to tackle this one but I need some help finding out how to replicate so if any one could share their camera and setup it would help

I tested the latest build you posted here in the comments and the error is always “timeout….” I keep wondering if it's just a few people's problem, or if others still use older versions. As I specified in other comments, the version I can use is 0.5.11, which at first glance seems to give no problems, but BI gives "No signal" at least once every 2 hours. Mc @QuantumEntangledAndy

[QuantumEntangledAndy]

Id appreciate a full log rather than just the word timeout. There are half a dozen different time out sources and the log should show which one.

Also on latest I can run on all my cameras for hours without issue. But I also don't have BI trying to constantly pull frames. So this is why I wanted to ask about your setup. I need details to replicate. For example do you use pause. Do you have a client always connected. Is this using UID or IP address discovery.

[QuantumEntangledAndy]

Looking at the code around timed out waiting to send media frame there is a 3 message buffer. This means that it will pause until there is space in the buffer before sending a frame after 3 messages.

The other end of the queue is a dedicated thread meant to pass the buffer onto gstreamer. There a LOT of code for this because of how so many clients expect the data to be formatted and so we can handle pausing. If I had to guess the code is getting overloaded here. Maybe the client makes multiple connections which results in processing many buffers.

Could you try this in your config

[[cameras]]
# Other camera options like UID etc
buffer_size = 0
splash = false

That will tell it not to use an internal buffer which will speed up that part of the code but will result in less smooth streams

[MicheleCardamone]

@QuantumEntangledAndy

HI. I tested the latest build you posted here in the comments with the settings buffer size 0 and splash false. The problem occurs as always. I am attaching the config file, the neolink error and the settings in blueiris to try to help you as much as possible. Feel free to ask me for help with what I can do! EDIT: The only different thing seems to be that it is only one cam that gives the error, while the other times, if I'm not mistaken, were 3.

BlueIris version: 5.7.8.0 Gstreamer 1.0 installed throught Chocolatey

image

[skylord123]

Using neolink:latest docker container got this issue again today.

It's only happening for the subStream this time. The main stream is still working for this camera.

Logs:

[2023-08-23T17:47:33Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel
[2023-08-23T17:47:33Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)
[2023-08-23T17:47:41Z INFO  neolink::rtsp] front_yard_door: Join Pause
[2023-08-23T17:47:41Z WARN  neolink::rtsp] front_yard_door: Retryable error: Timed out waiting to send Media Frame

    Caused by:
        deadline has elapsed
[2023-08-23T17:47:49Z INFO  neolink_core::bc_protocol] front_yard_door: Trying TCP discovery
[2023-08-23T17:47:49Z INFO  neolink_core::bc_protocol] front_yard_door: TCP Discovery success at 192.168.1.193:9000
[2023-08-23T17:47:49Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera time is already set: 2023-08-23 11:47:49.0 +06:00:00
[2023-08-23T17:47:49Z INFO  neolink::rtsp::states::loggedin] front_yard_door: Camera reports firmware version v2.0.0.843_17061500
[2023-08-23T17:47:49Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Main Stream (Clear)
[2023-08-23T17:47:49Z INFO  neolink::rtsp::states::streaming] front_yard_door: Starting video stream Sub Stream (Fluent)
[2023-08-23T17:47:57Z WARN  neolink_core::bc_protocol::connection::bcconn] Reaching limit of channel
[2023-08-23T17:47:57Z WARN  neolink_core::bc_protocol::connection::bcconn] Remaining: 0 of 100 message space for 4 (ID: 3)

The camera having the issue is front_yard_door. Reaching limit of channel looks like something that may help figure it out.

EDIT: The main stream stopped working shortly after making this comment. There are no additional logs after that happened (last lines still matches what I posted above).

@QuantumEntangledAndy if you want to make a test version with extra logging on another dockerhub tag I can run it and give you the full log. Anything that helps figure this out.

[QuantumEntangledAndy]

Yes I'm actually working on a larger refractor to try and eliminate this but it will take some time and lots of testing.

[MicheleCardamone]

Yes I'm actually working on a larger refractor to try and eliminate this but it will take some time and lots of testing.

Thank you for the work you are doing. As far as I'm concerned, I'm available to carry out any type of test. Mc @QuantumEntangledAndy

[skylord123]

In the mean time you can wire together something in Node-RED to auto restart Neolink when the streams stop working.

Since I am using Xeoma I was able to add the Problem Detector node connected to a HTTP Sender node. When it detects an issue it will call a given URL and pass the problem information. I just setup an endpoint on Node-RED for this and have it use the NR module Dockerode to restart the container.

Bonus is it will only restart Neolink if it is already running. That way if you shut it down it wont just start back up unintentionally.

If anyone else wants to use this: https://gist.github.com/skylord123/434a97ba513287046731b9e07b6e506a

[MicheleCardamone]

Hi, Any update? @QuantumEntangledAndy

[QuantumEntangledAndy]

On the refactor? It will take over a week, it's quite a lot of work and its only me working on it while also having actual life things too. Hi, Any update? and a ping are not helping. If you want to see code pushes it is going onto the refractor/neo_reactor branch

[apedance]

If you are on Blue Iris you can enable the watchdog and use a simple script like ...

taskkill /IM neolink.exe /F C:\Users\name\Neolink\runneolink.cmd

to restart neolink.

[MicheleCardamone]

If you are on Blue Iris you can enable the watchdog and use a simple script like ...

taskkill /IM neolink.exe /F

C:\Users\name\Neolink\runneolink.cmd

to restart neolink.

it would work, only that every 2/3 hours the system will have holes for a few seconds, which is unacceptable for a video surveillance system. But perhaps it is a better solution than using version 0.5.11 which is the only one that works for me that generates a "No signal" every 2 hours

[MicheleCardamone]

@QuantumEntangledAndy Hi, how is going with the refactor? Is there anything the community can help you test?

[QuantumEntangledAndy]

The main backend is moved over to the new design and the rtsp part is done. Currently working on moving the mqtt into the new model. Last testable build was https://github.com/QuantumEntangledAndy/neolink/actions/runs/6089212723 but this one was before I put in the pause stuff. You can try it if you want. Later builds are all WIP and not at testable points. Be aware that this is all still being revised.

[MicheleCardamone]

The main backend is moved over to the new design and the rtsp part is done. Currently working on moving the mqtt into the new model. Last testable build was https://github.com/QuantumEntangledAndy/neolink/actions/runs/6089212723 but this one was before I put in the pause stuff. You can try it if you want. Later builds are all WIP and not at testable points. Be aware that this is all still being revised.

Hi, first of all thank you for the work you are doing. I tried this version and it doesn't seem to work for me. I always left the same config file but in blue iris I have "no signal" @QuantumEntangledAndy MC

[QuantumEntangledAndy]

It's usually best to report neolink issues over client issues. I don't own blue iris and I'm sure even if I did no signal seems to be such a generic error it dosent reveal the root cause. What does the log say?

[skylord123]

Last testable build was https://github.com/QuantumEntangledAndy/neolink/actions/runs/6089212723 but this one was before I put in the pause stuff. You can try it if you want.

Is this the same build as tag refractor-neo_reactor on dockerhub ?

If so I just tried this out and none of my 3 camera streams were coming through. This just kept spamming in the console:

[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.399s, Runtime: 9.468664s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.370008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.370008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.549s, Runtime: 9.531507s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.549s, Runtime: 9.531129s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.370008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.549s, Runtime: 9.598735s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.370008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.549s, Runtime: 9.669312s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.520008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.520008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.699s, Runtime: 9.73394s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.699s, Runtime: 9.733562s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Frame recieved with ts: 2790.520008s
[2023-09-11T16:59:33Z INFO  neolink::rtsp] Setting PTS: 9.699s, Runtime: 9.804089s

If this is not the same build you mentioned, how do I match up the tag on dockerhub to the github action?

It's usually best to report neolink issues over client issues.

I tested this tag in VLC as well to remove my DVR software Xeoma from being the problem. Issue happened in VLC as well. Stream couldn't connect.

[QuantumEntangledAndy]

That's the right build and the spamming was part of my debug at the time. It is saying the a frame was received and then sent out to the rtsp client.

If it's not working then not much to do bit wait. I was hoping that it will at least connect on that build since I was able to with ffplay but if not I'll comeback and check again once the mqtt bit updated.

[QuantumEntangledAndy]

I think the rtsp is ready for testing with the build here or docker pull quantumentangledandy/neolink:refractor-neo_reactor. Mqtt hasn't been tested properly yet so just test the rtsp please.

[MicheleCardamone]

I think the rtsp is ready for testing with the build here or docker pull quantumentangledandy/neolink:refractor-neo_reactor. Mqtt hasn't been tested properly yet so just test the rtsp please.

Hi! Tested, it seems to be quite similar to the previous build. I can't see any stream in blueiris, and if it does, it disappears shortly after.

[skylord123]

I just tried this out and none of the streams are coming through for me:

[2023-09-14T15:20:48Z INFO  neolink] Neolink 5561236323694be0663b2fb950a8edcd0dbb3f85 release
[2023-09-14T15:20:49Z INFO  neolink::rtsp] Starting RTSP Server at 0.0.0.0:8554
[2023-09-14T15:20:49Z INFO  neolink::rtsp] driveway: Rtsp Staring
[2023-09-14T15:20:49Z INFO  neolink::rtsp] front_yard_door: Rtsp Staring
[2023-09-14T15:20:49Z INFO  neolink::rtsp] backyard: Rtsp Staring
[2023-09-14T15:20:49Z INFO  neolink::utils] driveway: Connecting to camera at Address: 192.168.1.195:9000
[2023-09-14T15:20:49Z INFO  neolink::utils] front_yard_door: Connecting to camera at Address: 192.168.1.193:9000
[2023-09-14T15:20:49Z INFO  neolink::utils] backyard: Connecting to camera at Address: 192.168.1.194:9000
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] front_yard_door: Trying TCP discovery
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] backyard: Trying TCP discovery
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] driveway: Trying TCP discovery
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] driveway: TCP Discovery success at 192.168.1.195:9000
[2023-09-14T15:20:49Z INFO  neolink::utils] driveway: Logging in
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] backyard: TCP Discovery success at 192.168.1.194:9000
[2023-09-14T15:20:49Z INFO  neolink::utils] backyard: Logging in
[2023-09-14T15:20:49Z INFO  neolink_core::bc_protocol] front_yard_door: TCP Discovery success at 192.168.1.193:9000
[2023-09-14T15:20:49Z INFO  neolink::utils] front_yard_door: Logging in
[2023-09-14T15:20:49Z INFO  neolink::utils] backyard: Connected and logged in
[2023-09-14T15:20:49Z INFO  neolink::common::camthread] backyard: Camera time is already set: 2023-09-14 9:20:48.0 +06:00:00
[2023-09-14T15:20:49Z INFO  neolink::utils] front_yard_door: Connected and logged in
[2023-09-14T15:20:49Z INFO  neolink::utils] driveway: Connected and logged in
[2023-09-14T15:20:49Z INFO  neolink::common::camthread] front_yard_door: Camera time is already set: 2023-09-14 9:20:48.0 +06:00:00
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] backyard: Model RLC-410
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] backyard: Firmware Version v2.0.0.1288_18020701
[2023-09-14T15:20:49Z INFO  neolink::common::camthread] driveway: Camera time is already set: 2023-09-14 9:20:48.0 +06:00:00
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] front_yard_door: Model RLC-420
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] front_yard_door: Firmware Version v2.0.0.843_17061500
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] driveway: Model RLC-423WS
[2023-09-14T15:20:49Z INFO  neolink::common::neocam] driveway: Firmware Version v2.0.0.1441_19032113_v1.0.0.30
[2023-09-14T15:20:49Z INFO  neolink::rtsp] driveway: Avaliable at ["/driveway/main", "/driveway/Main", "/driveway/mainStream", "/driveway/MainStream", "/driveway/Mainstream", "/driveway/mainstream", "/driveway"]
[2023-09-14T15:20:49Z INFO  neolink::rtsp] backyard: Avaliable at ["/backyard/main", "/backyard/Main", "/backyard/mainStream", "/backyard/MainStream", "/backyard/Mainstream", "/backyard/mainstream", "/backyard"]
[2023-09-14T15:20:49Z INFO  neolink::rtsp] driveway: Avaliable at ["/driveway/sub", "/driveway/Sub", "/driveway/subStream", "/driveway/SubStream", "/driveway/Substream", "/driveway/substream"]
[2023-09-14T15:20:49Z INFO  neolink::rtsp] front_yard_door: Avaliable at ["/front_yard_door/main", "/front_yard_door/Main", "/front_yard_door/mainStream", "/front_yard_door/MainStream", "/front_yard_door/Mainstream", "/front_yard_door/mainstream", "/front_yard_door"]
[2023-09-14T15:20:49Z INFO  neolink::rtsp] backyard: Avaliable at ["/backyard/sub", "/backyard/Sub", "/backyard/subStream", "/backyard/SubStream", "/backyard/Substream", "/backyard/substream"]
[2023-09-14T15:20:49Z INFO  neolink::rtsp] front_yard_door: Avaliable at ["/front_yard_door/sub", "/front_yard_door/Sub", "/front_yard_door/subStream", "/front_yard_door/SubStream", "/front_yard_door/Substream", "/front_yard_door/substream"]

[QuantumEntangledAndy]

@MicheleCardamone you have a panic at the end there could you set the rust backtrace variable that it is recommending and try again and show me the log. That way I can know which line it is on