I try to use the docker in the ubuntu without sucess

[nunokaneco]

Hello Team

I just try to use the docker as mentioned in the readme without success, I also try to execute the commands after download the current version and unzip also created the myconfig file, but I can't execute the command neolink --config my_config.toml

Can anyone please help me in order to get this to work ?

Thank you and best regards

[QuantumEntangledAndy]

This is not a bug. But I take it you are not familiar with terminals and exceutables.

1. Download the latest version
2. Unzip it
3. Copy the file to the folder /usr/local/bin/

cd the_location_you_unzipped_to
sudo cp neolink /usr/local/bin/neolink

4. Make it executable

sudo chmod +x /usr/local/bin/neolink

5. Check neolink runs

neolink --help

6. Make and save a my_config.toml with the right settings
7. Run neolink with the config

neolink --config my_config.toml

Send logs or pictures of anything you have trouble with.

Read the other issues people have had: #126.

Read the documentations: https://github.com/thirtythreeforty/neolink/tree/master/docs

[nunokaneco]

This is not a bug. But I take it you are not familiar with terminals and exceutables.

1. Download the latest version
2. Unzip it
3. Copy the file to the folder /usr/local/bin/

cd the_location_you_unzipped_to
sudo cp neolink /usr/local/bin/neolink

1. Make it executable

sudo chmod +x /usr/local/bin/neolink

1. Check neolink runs

neolink --help

1. Make and save a my_config.toml with the right settings
2. Run neolink with the config

neolink --config my_config.toml

Send logs or pictures of anything you have trouble with.

Read the other issues people have had: #126.

Read the documentations: https://github.com/thirtythreeforty/neolink/tree/master/docs

Thank you for your reply, now it's working again more our less.... I just have success executing the neolink but now I'm facing this issue

./neolink --config my_config.toml
[2021-01-25T11:45:20Z INFO  neolink] Neolink 055d731feca7362e02d227199c43aa00f8526638 release
[2021-01-25T11:45:20Z WARN  neolink] The format config option of the camera has been removed in favour of auto detection.
[2021-01-25T11:45:20Z INFO  neolink] driveway: Connecting to camera at 192.168.2.168:9000
[2021-01-25T11:45:20Z INFO  neolink] driveway: Connecting to camera at 192.168.2.168:9000
[2021-01-25T11:45:20Z INFO  neolink] driveway: Connected and logged in
[2021-01-25T11:45:20Z INFO  neolink] driveway: Starting video stream subStream
[2021-01-25T11:45:20Z INFO  neolink] driveway: Connected and logged in
[2021-01-25T11:45:20Z INFO  neolink] driveway: Camera time is already set: 2021-01-25 11:45:20 +0
[2021-01-25T11:45:20Z INFO  neolink] driveway: Camera reports firmware version v3.0.0.42_20062900
[2021-01-25T11:45:20Z INFO  neolink] driveway: Starting video stream mainStream
[2021-01-25T11:46:59Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-25T11:47:00Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream

Can you please help me understanding what is this error ?

Thank you and best regards

[QuantumEntangledAndy]

Everything seems to be working have you tried to connect with an rtsp client like ffplay or VLC?

You have a warning about a new magic code. This should not stop the stream from working it just means your camera is sending a data type we haven't seen before. Could you tell us what your camera model is? If you know how to. Use wireshark you could send us the data packets of your new camera and we can study what it means. But a wireshark dump is a technical subject and may be too difficult for you.

[nunokaneco]

Everything seems to be working have you tried to connect with an rtsp client like ffplay or VLC?

This WARN appears when I try to access the stream over HA Home Assistant, from the VLC is working well without any issue, The Camera model is the REOLINK E1, regrading the wireshark I will try and share

Thank you and best regards

[QuantumEntangledAndy]

The WARN is coming from the camera side of the connection not the HA end so they should not be related.

I use HA at home too (with an E1 as well), make sure you set HA to use TCP and not UDP when connecting to neolink.

This is my ha config

# Cameras
camera:
  - platform: ffmpeg
    name: Live CAMNAME
    input: -rtsp_transport tcp -probesize 500 -i rtsp://127.0.0.1:8554/CAMNAME/subStream

[QuantumEntangledAndy]

Don't worry about the wireshark as I have an E1 with dumps already I think in this case it is just a truncated packet from the stream trying to start mid packet

[thirtythreeforty]

Hey guys glad you got this working - I'm going to convert to a discussion. Feel free to keep talking

[nunokaneco]

Hello

I still have a issue when I try to use the reolink camera E1 over the neolink when I try to start the neolink and after starting the stream over the VLC or Home Assistant I receive the following

[2021-01-31T17:36:29Z INFO  neolink] driveway: Connecting to camera at 192.168.2.168:9000
[2021-01-31T17:36:30Z INFO  neolink] driveway: Connected and logged in
[2021-01-31T17:36:30Z INFO  neolink] driveway: Camera time is already set: 2021-01-31 17:34:38 +0
[2021-01-31T17:36:31Z INFO  neolink] driveway: Connected and logged in
[2021-01-31T17:36:31Z INFO  neolink] driveway: Starting video stream subStream
[2021-01-31T17:36:31Z INFO  neolink] driveway: Camera reports firmware version v3.0.0.42_20062900
[2021-01-31T17:36:31Z INFO  neolink] driveway: Starting video stream mainStream
[2021-01-31T17:36:48Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-31T17:36:51Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-31T17:37:00Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-31T17:37:00Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-31T17:37:00Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream
[2021-01-31T17:37:05Z WARN  neolink::bc_protocol::media_packet] Possibly truncated packet or unknown magic in stream

And I can't view the image stream

This is my config in the YAML file

ffmpeg:
 ffmpeg_bin:  /usr/bin/ffmpeg

# Cameras
camera:
  - platform: ffmpeg
    name: Reolink E1
    input: -rtsp_transport tcp -probesize 500 -i rtsp://192.168.2.138:8554/driveway/subStream

And this is the my config file on neolink

[[cameras]]
name = "driveway"
username = "admin"
password = " my password  "
address = "192.168.2.168:9000"
format= "h264"

Can you please help me understant this issue ?

Thank you and best regards

[nunokaneco]

Just for your info If i start first the VLC and load the stream the stream works great but if I try to load after try to open the tab on the Home Assistant I can't load the stream even in the VLC or in the HA

[nunokaneco]

And if I try to access the stream of 2 different cameras like this in the YAML I can't load both but if I comment or remove one of the parameters for one of this cameras I have a stream working

camera:

• platform: ffmpeg
  name: camera
  input: rtsp://admin:My PASSWORD @192.168.2.XXX:554
  name: Reolink E1
  input: -rtsp_transport tcp -probesize 500 -i rtsp://192.168.2.XXX:8554/driveway/subStream

  Thank you for your support

[QuantumEntangledAndy]

Could you try with ffplay or ffmpeg I can understand the logs better then. Currently there's nothing in the pictures but genetic errors. It may also help to have neolink with debug logs again while it is connecting.

You also may have more success if you turn off the HD stream in neolink.

[[cameras]]
name = "driveway"
username = "admin"
password = " my password  "
address = "192.168.2.168:9000"
format= "h264"
stream = "subStream"

[nunokaneco]

Hello

I tried with the subStream option but i still have some issues when I try to view the 2 streams on the HA home Assistant only one at the time is possible and I don't know why .. once the other streams are working ...

Thank you for your support