Posts made by Steven Kan_61128021664

Steven Kan_61128021664

My BeeCam is a Raspberry Pi3/Raspbian Stretch w/freshly compiled ffmpeg version N-89882-g4dbae00bac running this as a service:

#!/bin/bash
cd /usr/local/bin/
while true
do
./ffmpeg -re -thread_queue_size 512 -rtsp_transport tcp -i 
"rtsp://anonymous:password@192.168.1.11:554" -i WilliamTellOverture.mp3 
-vcodec copy -acodec copy -t 00:11:51 -f flv 
"rtmp://a.rtmp.youtube.com/live2/my-youtube-streaming-key"
sleep 10s
done

where 192.168.1.11 is my spiffy new Reolink RLC-423S, and -t 00:11:51 is the length of my royalty-free MP3. This normally works quite well:

https://www.youtube.com/user/IAmTheWaterbug/live

and it loops continuously. The YT stream will glitch when it restarts, but the stream resumes with only about 15 seconds of video lost. It ran continuously overnight for at least 8 hours (e.g. many loops) before I started fiddling with it.

I changed the sleep to 5s, and that doesn't seem to bother it.

But on occasion I've done a sudo systemctl stop StreamToYouTube followed by sudo systemctl start StreamToYouTube, within 1-2 seconds (e.g. as fast as I can type Up Up Up and Enter), and sometimes when I do that, the stream fails, and ffmpeg starts dumping:

[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq e680 expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq 93ab expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq 93ac expected=0b49
[rtsp @ 0x302c2f0] RTP: PT=60: bad cseq e682 expected=0b49

endlessly.

Rebooting the Pi doesn't fix this (e.g. the YT stream still fails, and sudo systemctl status StreamToYouTube returns the same stream of "bad cseq" errors), but rebooting the RLC-423S does fix it. I'm wondering what exactly that error means.

During the "failed" state, the camera appears to be working properly from other clients, e.g. I can launch the Reolink.app on my Mac or view the camera's web page from any browser, and the video looks fine.

But for some reason the RTSP stream goes funky in a way that ffmpeg can't resolve.

It's quite repeatable if I stop/start the service quickly, but restarting with a 5 second pause in my script doesn't seem to bother it.

Thanks!
BadCseq.png

Steven Kan_61128021664

I wanted to mount my spiffy new RLC-423S against a fence in my apiary:

[url=http://www.kan.org/download/ApiaryPanorama.jpg][img]http://www.kan.org/download/ApiaryPartial.jpg[/img][/url]
(click to ginormify)

so that the camera faces inward, toward the hive entrances the face to the right (they've been moved backward/eft by about 18" since that photo was taken).

The vertical bars in that fence are square in cross-section, so I need something like a pole mount.

I ended up [url=https://smile.amazon.com/gp/product/B072JCQDCW/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1]buying this box[/url], and modifying it as follows:

[img]http://www.kan.org/pictures/Enclosure.jpg[/img]

Holes drilled to match the camera, to bring the cables into the box, and for the [url=https://smile.amazon.com/gp/product/B01EJLZSI4/ref=oh_aui_search_detailpage?ie=UTF8&psc=1]waterproof egress[/url]:
[img]http://www.kan.org/pictures/Drilled.jpg[/img]

[url=https://www.homedepot.com/p/DANCO-6-in-x-6-in-Rubber-Packing-Sheets-59859/303689103]Gasket material[/url], cut and punched to match:
[img]http://www.kan.org/pictures/Gasket.jpg[/img]

Wired up with a [url=https://smile.amazon.com/gp/product/B01J6JP8XE/ref=oh_aui_search_detailpage?ie=UTF8&psc=1]passive POE extractor[/url] and a short length of Cat5e. The matching injector is at the other end of the cable, along with the bundled Reolink power supply. This camera also works with 802.3af, but I don't have a POE switch down in the shed where this is all connected. This mass of cabling is why I needed the enclosure. Reolink does supply a waterproof coupling for the Ethernet connection, but they don't supply a way to protect the other cables in the octopus. And I ended up need every cubic inch inside the box. Once it's all coiled up, it's a pretty tight fit:
[img]http://www.kan.org/pictures/Connected.jpg[/img]

All screwed together. I needed some 1/4-20 x 3/4" bolts and nuts to attach the camera to the lid, because Reolink supplies only wood screws and drywall anchors. I put a dab of silicone into the original cable egress hole on the camera housing (not shown). I also have half a sheet of that rubber packing material glued to the back side, where it will snug up against the fence:
[img]http://www.kan.org/pictures/Assembled.jpg[/img]

I couldn't find U-bolts the same width as the mounting holes in the enclosure, so I bought a length of [url=https://www.homedepot.com/p/1-4-in-20-tpi-x-36-in-Zinc-Plated-Threaded-Rod-802217/204274011]1/4-20 threaded rod[/url] and made my own and wrapped them with a bit of duct tape:
[img]http://www.kan.org/pictures/UBolts.jpg[/img]

Originally I thought I was going to put these on in the reverse orientation, and then put a length of metal on the opposite side of the post, but my U-bolts weren't bent perfectly, nor at a sharp enough angle to permit that, so I have the nuts on this side. The original thought was also why I put the cable egress on the side instead of the bottom, since I thought it was going to interfere with the U-bolt. This works better, because I need fewer pieces, but I do have to turn the nuts a lot, and it's a bit difficult to tighten the last few turns, with little clearance, wearing beekeeping gloves:
[img]http://www.kan.org/pictures/UBoltAttached.jpg[/img]

And here it is, in service. The rubber backing and the duct tape actually work very well to keep the camera secure against the fence. I don't have to tighten the nuts very much. In fact I need a lot of slack to move it up and down into position, because it really wants to stick to the fence:
[img]http://www.kan.org/pictures/Mounted.jpg[/img]

[url=https://www.youtube.com/user/IAmTheWaterbug/live]Live stream is here[/url], but it's intermittent while I'm testing:

[img]http://www.kan.org/pictures/BeeCam2018.jpg[/img]

The stream doesn't work all the time. I have a Raspberry Pi acting as an [url=https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=136381&start=125#p1150700]ffmpeg relay[/url] right now. It uses ffmpeg to grab the RTSP packets from the camera and push them to my RTMP YouTube channel. It does no resizing or re-encoding, but it does do some minor repackaging into flv format. It only takes a few CPU%, but it quits every so often for reasons that I'm still trying to figure out.

It would be nice if Reolink could offer a pole mount and a way to protect the other cables when their POE cameras are mounted outside, but not against a wall.

Steven Kan_61128021664

I'm using my spiffy new RLC-423S as a BeeCam!

BeeCamp2018

Live stream is here, when the ffmpeg relay station is working.

Some feature suggestions:

Allow lower resolutions via pixel binning, such as 1920 x 1080. For YouTube streaming the excess resolution just eats bandwidth and processing power for no benefit

Allow lower resolutions via cropping. For example the BeeCam is at its maximum optical zoom right now, but for some scenes I'd like to take a center crop of 1920 x 1080 and "zoom" in even further.

Include a built-in way to push the stream to a YouTube streaming channel.
- Right now I'm using a Raspberry Pi3 as an ffmpeg "relay station" to pull from the camera and push it to YT.
- But ffmpeg isn't doing much. The script is just:
  ./ffmpeg -re -thread_queue_size 512 -rtsp_transport tcp -i "rtsp://user:password@192.168.1.121:554" -i SomeMusic.mp3 -vcodec copy -acodec copy -t 01:00:00 -f flv "rtmp://a.rtmp.youtube.com/live2/my-youtube-streaming-key"
- That script does no decoding or re-encoding. The "-vcodec copy -acodec copy" just takes the stream, muxes it with the music, repackages it in "flv" format, and pushes it back out. It consumes << 10% CPU on a Raspberry Pi3 with a 700 MHz ARM.
- I had to download and compile ffmpeg for the Pi, but Reolink can probably to this with just a few lines of firmware code on the camera, because it's just repacking the video stream that's already been processed.

Allow configurable, restricted access to certain PTZ features
- I have 4 Locations set up on the camera to look at Hive 1, Hive 2, etc.
- There's no way to allow YouTube visitors to Call a Location, and I don't want to give anyone direct access to my camera, even as a Normal user.
- It would be nice to be able to set up a custom URL, such as http://mycamera.dyndns.org/control/OneTimeKeyGeneratedByReolinkApp/PTZLocation1, or something like that, to allow a public user to select the view.