Sounds interesting, AG, but not sure if I'm following you 100%
I tried many times to get motion detection working and failed repeatedly. I then had a really good chat with a lmce veteran who (after a few /deep breaths) put it simple and said "use motion detectors to detect motion."
It sounds as if you are saying here that you aren't setting up the camera as a child of the motion device. Is that correct? What is it a child of? Can you screenshot one of your setups so I can see without giving too much away.
Not that I'm wanting to toss motion, though, I got it set up no-problems first time and I'm loving the motion events and have all sorts of plans for working with them. But I would be interested to see how you set up the devices differently.... I could even potentially do both, I'd imagine, if there was some benefit to not going the motion-wrapper route.
Also a bit confused about your "video stream" story... that thing about doing "view source" to find the actual video stream, well, that's a given with IP cameras isn't it? I mean you always have to do that to get them working don't you (ie isolate the video stream URL and stick that in the camera template)?
This gives me real time video without the rest of the browser page, that URL is where I point my camera templates and haven't had an issue with any orbiter cam view.