Can't connect to Argus Pro 3 - HELP! Battery powered camera

[matfil92]

Describe the bug
I've configured Neolink but I can't connect to the camera, already tried different solution written in many post but without solution.

To Reproduce
Steps to reproduce the behavior. Example:

1. Create this configuration file:
   `
   bind = "0.0.0.0"
   bind_port = 8554

[[cameras]]
name = "camera"
username = "admin"
password = "PASS-OF-THE-CAMERA"
uid = "95270-FULLUID"`

3. Launch Neolink:
   When I launch Neolink i've this error

`
[2024-04-29T20:18:14Z ERROR neolink_core::bc_protocol::connection::udpconn] Udp write poll aborted
[2024-04-29T20:18:34Z INFO neolink_core::bc_protocol::connection::udpconn::discover] Trying remote discovery against reolink servers
[2024-04-29T20:18:34Z INFO neolink::rtsp] camera: Connecting to camera at UID: 952700078W777NDS
[2024-04-29T20:18:34Z INFO neolink::rtsp] camera: Logging in
[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::udpconn] Camera requested disconnect
[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::udpconn] Udp read poll aborted
[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::bcconn] Deserialization error: Deserialization error
[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::bcconn] caused by: I/O error
[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::bcconn] caused by: Connection dropped when reading from udp channel
[2024-04-29T20:18:34Z ERROR neolink::rtsp] Error streaming from camera camera, will retry in 15s: Failed to login to camera

Caused by:
    Dropped connection

[2024-04-29T20:18:34Z ERROR neolink_core::bc_protocol::connection::udpconn] Udp write poll aborted
`

Expected behavior
Correct Launch of the Neolink and RTSP protocol

Versions
Neolink run in Docker with Portainer
Neolink software: 0.4.0
Reolink camera model and firmware: Reolink Argus PRO 3 - build no 23072900 - ver firmware v3.0.0.2527_23072900

[QuantumEntangledAndy]

Please read #370, then try again using my fork mentioned in the issue. If it persists open an issue there