Comments (16)
Could you try this on the latest version? I noticed that sometimes the camera would drop up with a terminate if we spent too long between discovery completed and waiting for the login. So I changed the discovery hand-off a bit to help with this. Perhaps it can help you here.
from neolink.
tried latest version and it fires but takes some attempts
gc@scs:~/neolink $ ./neolink rtsp --config=conf.toml
[2023-04-24T06:42:13Z INFO neolink] Neolink 42ff221 release
[2023-04-24T06:42:13Z INFO neolink::rtsp] Starting RTSP Server at 0.0.0.0:8554
[2023-04-24T06:42:15Z INFO neolink_core::bc_protocol] Rear: Relay success 9xxxxxxxxxxxxxX at 20..xxx.xxx.xxx:51450
[2023-04-24T06:42:28Z WARN neolink::rtsp] Rear: Retryable error: Rear: Could not login to camera
Caused by:
0: IO Error: Custom { kind: Other, error: RelayTerminate }
1: Relay terminated the connection
[2023-04-24T06:42:31Z INFO neolink_core::bc_protocol] Rear: Relay success 9xxxxxxxxxxxxxX at 20..xxx.xxx.xxx:51450
[2023-04-24T06:42:45Z WARN neolink::rtsp] Rear: Retryable error: Rear: Could not login to camera
Caused by:
0: IO Error: Custom { kind: Other, error: CameraTerminate }
1: Camera terminated the connection
[2023-04-24T06:42:48Z INFO neolink_core::bc_protocol] Rear: Relay success 9xxxxxxxxxxxxxX at 20..xxx.xxx.xxx:51450
[2023-04-24T06:43:01Z WARN neolink::rtsp] Rear: Retryable error: Rear: Could not login to camera
Caused by:
0: IO Error: Custom { kind: Other, error: CameraTerminate }
1: Camera terminated the connection
[2023-04-24T06:43:04Z INFO neolink_core::bc_protocol] Rear: Relay success 9xxxxxxxxxxxxxX at 20..xxx.xxx.xxx:51450
==Battery==
Charge: 70%,
Temperature: 15°C,
LowPower: false,
Adapter: none,
ChargeStatus: none,
[2023-04-24T06:43:18Z INFO neolink::rtsp::states::loggedin] Rear: Camera time is already set: 2023-04-24 7:43:23.0 +00:00:00
[2023-04-24T06:43:19Z INFO neolink::rtsp::states::loggedin] Rear: Camera reports firmware version v3.0.0.715_21112344
[2023-04-24T06:43:19Z INFO neolink::rtsp::states::streaming] Rear: Starting video stream Main Stream (Clear)
[2023-04-24T06:43:19Z INFO neolink::rtsp::states::streaming] Rear: Starting video stream Sub Stream (Fluent)
==Battery==
Charge: 69%,
Temperature: 15°C,
LowPower: false,
Adapter: none,
ChargeStatus: none,
==Battery==
Charge: 68%,
Temperature: 15°C,
LowPower: false,
Adapter: none,
ChargeStatus: none,
still I get no stream
vlc log on rtsp://admin:[email protected]:8554/Rear
shows
live555 error: Failed to connect with rtsp://192.168.0.153:8554/Rear
satip error: Failed to setup RTSP session
-- logger module stopped --
from neolink.
Ok so it connects after a few times then. After which you just have trouble with VLC. I presume this is to do with the VLC issues I'm tracking in #68. If you could maybe try that build and the seetings shown in the PR
from neolink.
Sorry was just using vlc as an example it does not actually stream to anything , also tried shinobi, zoneminder and frigate all fail but wiil try your suggestion.. Thank you for your help
from neolink.
After changes to vlc exact same error,
also noticed that after a period of time neolink loses connectivity to the camera, after the camera terminates the connection and the only way to get back is terminate and restart neolink
from neolink.
Is there any reason why I only ever seem to see relay connections with your camera? That usually only happens if your on different networks. It should still work because that's how I test but it does usually mean that we get extra terminate commands.
There's not much I think I can do about the terminates without observing them more myself. They usually only happen with me if the connection is flakey and the camera drops us for having an unstable connection.
from neolink.
Hi Andy Can confirm my pc , the raspberry pi 4 running neolink and the cameras are all on the same 192.168.0. subnet.
from neolink.
Hi Andy had a mind blowout and tested neolink on my windows pc and it worked instantly on vlc etc. this means the issue lies with raspianpi os and dietpi os, have tried both and no firewall is setup by default and netstat shows port 8554 is listening
RPI is a pi 4 with 4gb ram booting from a 1tb ngff ssd connectivity via rj45. the conf file I use is the same on both windows and RPI . is it possible I am missing a setting somewhere?
from neolink.
I really cannot tell since this seems to be a network/firewall type of thing.
Do you know the IP address of your camera? If so have you added it into the addr field of the config? That will allow neolink to use it during discovery which will help with local networks where broadcasts are forbidden.
from neolink.
Could be something at the router too. If your rpi is on Ethernet and camera on Wi-Fi maybe there's some sort of network isolation or the bridge dosent forward broadcasts etc.
from neolink.
I will deep further in to this and keep you updated, it may help someone in the future. And thank you for all your help up to now
from neolink.
Can now confirm that the issue lies with specific operating systems. Raspberrypi os and dietpi os definitely fail to work, windows and ubuntu server run like a dream Thank you for all the assistance for this awesome product
from neolink.
I had a recent user report that windows dosent work and that rpi does so it's likely not as simple as that. Still glad it's working for you.
from neolink.
What was your rpi model and OS? I'll see if I can replicate on one of my pis
from neolink.
from neolink.
Thanks. I mostly test on pi3s as my 4 is busy with other things. But I'll see if it makes any difference
from neolink.
Related Issues (20)
- Custom("missing field `FloodlightStatus`") results in two connection attempts HOT 10
- Floodlight latched when set to trigger from motion HOT 2
- ffprobe 503 Service Unavailable
- Delayed MQTT Motion HOT 5
- Unable to stream from E1 using the latest neolink docker image HOT 2
- Can't connect to Cameras with 0.6.3-rc.1
- <jemalloc>: Unsupported system page size - docker on Debian 12 on rpi5 HOT 10
- Getting Neolink in Home Assistant working HOT 11
- ONVIF Support and Scrypted Two Way Audio HOT 1
- 'RTSP Staring' message should say 'RTSP Starting' HOT 1
- Can't integrate with Home Assistant. HOT 1
- Can't connect to Reolink Argus Track HOT 3
- error resol-vbus config issues HOT 4
- Possible infinite loop in NeoReactor push notification... HOT 9
- mainStream issues
- Neolink does not connect to MQTT broker. WARN: Connection Lost: Dropped connection HOT 2
- Document the Binary XML protocol & Update wireshark dissector. HOT 6
- Neolink causing excessive battery usage
- Registration with reolink servers failed HOT 12
- Neolink Memory Leak / Errors HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neolink.