Closed CodeFatherG closed 1 month ago
Sorry I have just done further testing, It looks like the floodlight does turn off but its a lot longer when running neolink vs without
We don't make any changes to the camera directly. So maybe this is normal behaviour for the camera when there's an active connection. Not really something I can address.
Describe the bug
When using mqtt and "Night Smart Mode" is set, the floodlight remains on after motion is no loner detected. When neolink is not running, the floodlight turns off after motion.
To Reproduce
Steps to reproduce the behavior. Example:
Define RTSP user
[[users]] name = "admin" pass = ...
Front Camera
[[cameras]] name = "front_door_camera" discovery = "local" # Discover local username = "admin" # Camera user password = ... address = "..." # Reserved ip of camera uid = "..." # Camera UID stream = "Main" idle_disconnect = true # Disconnect on idle for battery [cameras.pause] on_motion = true # Should pause when no motion on_client = true # Should pause when no rtsp client [cameras.mqtt] [cameras.mqtt.discovery] topic = "homeassistant" # Enable Discovery with the following controls features = ["Floodlight", "Camera", "Motion", "Reboot", "Battery", "Siren"]
[mqtt] broker_addr = "127.0.0.1" # local broker port = 1883 credentials = ...
version: '3.8' services: neolink: image: quantumentangledandy/neolink:latest command: ["/usr/local/bin/neolink", "mqtt-rtsp", "--config=/etc/neolink.toml"] container_name: neolink ports:
Expected behavior
floodlight is turned off when motion is not detected
Logs
Versions
Neolink software: latest Reolink camera model and firmware: Model Argus Eco Ultra v3.0.0.2773_23100910