Reolink RL-410W has a green screen
See original GitHub issueReolink RL-410W now has a green screen showing in Frigate NVR. I have not changed anything in yml file, however, I have done an Home Assistant core update recently. The green screen appears after that. I use Raspberry pi 4b, with home assistant.
Camera yml file:
cameras:
driveway:
ffmpeg:
input_args:
- -avoid_negative_ts
- make_zero
- -fflags
- nobuffer
- -flags
- low_delay
- -strict
- experimental
- -fflags
- +genpts+discardcorrupt
- -rw_timeout
- '5000000'
- -use_wallclock_as_timestamps
- '1'
inputs:
- path: rtmp://ipaddress/bcs/channel0_sub.bcs?channel=0&stream=0&user=xxx&password=xxx
roles:
- detect
- rtmp
- clips
- record
clips:
enabled: True
pre_capture: 5
post_capture: 5
objects:
- person
required_zones: []
retain:
default: 10
objects:
person: 5
car: 5
cat: 5
dog: 5
horse: 5
truck: 5
bicycle: 5
snapshots:
enabled: True
timestamp: False
bounding_box: False
crop: False
height: 175
required_zones: []
retain:
default: 10
objects:
person: 5
car: 5
cat: 5
dog: 5
horse: 5
truck: 5
bicycle: 5
record:
enabled: False
retain_days: 5
width: 640
height: 352
fps: 4
Log error:
ffmpeg.driveway.detect ERROR : [tcp @ 0x55a958cc50] Connection to tcp://ipaddress:1935 failed: Connection refused
ffmpeg.driveway.detect ERROR : [rtmp @ 0x55a958c780] Cannot open connection tcp://192.168.1.10:1935
ffmpeg.driveway.detect ERROR : rtmp://ipaddress/bcs/channel0_sub.bcs?channel=0&stream=0&user=xxx&password=xxx: Connection refused
frigate.video INFO : driveway: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
frigate.video INFO : driveway: ffmpeg process is not running. exiting capture thread...
Could you please help? Many thanks Kate
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Green Image - Reolink Support
Solution: If the live view image is green all the time and never come back to normal, then it could be the hardware...
Read more >Frigate green screen with Reolink cameras over RTMP or HTTP
The cameras work perfectly well with RTMP streams running in motioneye which is running in parallel on the same machine until i figure...
Read more >Reolink Gotchas - Blue Iris
And all it keeps freezing with grey screen. Is there any hope with these cameras or should I just return them? Image.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Check out the below. Try removing all of those extra input_args. Also try adding the global_args below to your config. I had some luck with these since it seems that the reolink cameras sometimes take a while to start streaming rtmp. Also make sure the firmware on your cameras is up to date. Finally are you sure your “height” is set right at 352? I don’t think this is a valid option for the reolink substream. As Blake mentioned though, probably none of this matters until you get frigate to connect to the camera. Can you ping the camera from the frigate machine? This will work…its something about your configuration that is breaking it.
ffmpeg: input_args: - -avoid_negative_ts - make_zero
front_door_cam: ffmpeg: inputs: - path: rtmp://10.1.1.1/bcs/channel0_sub.bcs?channel=0&stream=0&user=username&password=password global_args: -analyzeduration 1000M -probesize 1000M roles: - detect - path: rtmp://10.1.1.1/bcs/channel0_main.bcs?channel=0&stream=0&user=username&password=password roles: - clips - rtmp height: 480 width: 640 fps: 4
After a week of green screen , my camera is now back to normal. Thank you everyone.