Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All set up, but RTSP can't connect #365

Open
3cfix666 opened this issue Jul 25, 2023 · 5 comments
Open

All set up, but RTSP can't connect #365

3cfix666 opened this issue Jul 25, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@3cfix666
Copy link

3cfix666 commented Jul 25, 2023

Reolink B800
set below
help


# A bind value of 0.0.0.0 means any network this computer can access
# You can chage this to a specfic network e.g. "192.168.1.101" here
# Or to no networks e.g. this computer only "127.0.0.1"
bind = "0.0.0.0"

# Default port is 8554 but you can change it by uncommenting the following
# bind_port = 8554

# Uncomment the following and supply a path to a valid PEM
# to activate TLS encryption.
# The PEM should contain the certificate and the private key
# If TLS is activated you must connect with "rtsps://" and not "rtsp://"
# certificate = "/path/to/pem/with/cert/and/key"

# Choose if the client is required to provide a certificate signed by the server's CA.
# none|requested|required - default none
# tls_client_auth = "required"

# You can password protect the rtsp server mount points by adding users
# like the following me and someone. If you do not add [[users]]
# then anyone can connect without a password or username
# To access such a stream try using a url such as "rtsp://me:[email protected]/driveway"

# [[users]]
# name = "me"
# pass = "mepass"
#
# [[users]]
# name = "someone"
# pass = "someonepass"


[[cameras]]
name = "B800"
username = "admin"
password = "Aa123456"
address = "192.168.0.102:9000"
# mqtt.broker_addr = "192.168.1.122"
# mqtt.port = 1883
# mqtt.credentials = ["mqtt_user", "mqtt_password"]
# MQTT Discovery: https://www.home-assistant.io/integrations/mqtt/#mqtt-discovery
# mqtt.discovery.topic = "homeassistant" # Uncomment to enable
# If using discovery, _ characters are replaced with spaces in the name and title case is applied
# mqtt.discovery.features = ["floodlight"] # Uncomment if this camera has a spotlight/floodlight

# If you use a battery camera: **Instead** of an `address` supply the uid
# as follows
# uid = "ABCD01234567890EFG"

# By default any of the users can connect (or anyone at all if no users are specfied)
# You can uncomment the following to permit only specfic users
# permitted_users = [ "me" ]

# By default "both" "mainStream" and "subStream" are connected
# If your device has user connection limits try a single stream instead.
# stream = "mainStream"

# By default neolink will use any means to connect to the camera
# from a UID
# This include relaying via reolink servers
# This variable `discovery` controls the method of UID discovery
# - Possible values
# "relay" # Any means including connecting and transmitting through reolink
# "map" # Register our local ip address with reolink and ask the camera to connect to us but don't relay data through reolink
# "remote" # Register our local ip address with reolink but only permit same network connections (useful if broadcast is not possible)
# "local" # Do not contact reolink servers at all. Rely soley on local UDP broadcast based discovery
#
# "cellular" # Cellular camera only support Relay and Map to speed up connecting to them this option will skip the local/remote
#
# discovery = "relay"

# Certain types of camera emit status messages (such as battery levels)
#
# By default we hide these status messages from the user but you can instead requst that
# they be printed to stdout using print_format
#
# Valid values are:
# - None
# - Human
# - Xml
#
# print_format = "None"

# Internally neolink uses a buffer to improve delivery of frames at their actual times
# A large buffer can work even for large interupts in the connection with the camera
# A small buffer will reduce the latency introduced
# buffer_size: 100

# Over long periods of time the camera buffer can exhaust with no means of recovery
# to combat this a time stretching stratery is employed where the stream is slowed
# as the buffer is exhausted and sped up when full
# this can keep the camera and rtsp streams in sync and reduce buffer exhaustions
#
# HOWEVER if there is real latency issues (such as too high a bitrate)
# then smoothing can result in a stream appearing in slow motion
#
# you can disable and enable this feature here
# use_smoothing: true


[[cameras]]
name = "B801"
username = "admin"
password = "Aa123456"
address = "192.168.0.102:9000"
# If you use a battery camera: **Instead** of an `address` supply the uid
# as follows
# uid = "ABCD01234567890EFG"

# If you use an NVR that relays several camera connections you can choose which
# camera to connect to with by setting the `channel_id`
#
# By default channel_id = 0. Eg the first connected camera on the device
# **Note**: that unlike in the offical client the  numbering starts from 0 not 1.
# An 8 channel NVR would have channels 0 through 7
# channel_id = 0
@3cfix666 3cfix666 added the bug Something isn't working label Jul 25, 2023
@QuantumEntangledAndy
Copy link
Collaborator

Everything seems fine here. What is the error in your rtsp client.

@3cfix666
Copy link
Author

Can't access it with VLC or potplayer
Is my RTSP connection wrong?
can you help me give me the correct link

@sazern
Copy link

sazern commented Jul 27, 2023

i had the same problem. My issue was that the name of the camera started with a capital letter.
Changed Pool to pool in the config and then it worked.

@3cfix666
Copy link
Author

我有同樣的問題。我的問題是相機的名稱以大寫字母開頭。 將配置中的 Pool 更改為 pool,然後就可以了。

Can you post your config?
What NEOLINK version do you use?
I changed the name to lowercase, and it's the same with all numbers.
Is it convenient to pack your file directory as a whole?
grateful

@QuantumEntangledAndy
Copy link
Collaborator

i had the same problem. My issue was that the name of the camera started with a capital letter. Changed Pool to pool in the config and then it worked.

This depends on the client, some clients will lowercase your url which caused issues. The latest build should address this as it tries to serve on multiple end points such as Cammy01 and cammy01 automatically for you.

Also this issue should be on my fork not on thirtythreeforty since it is using my forks version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants