I have been happily using ZM for a couple of years now, running on my PC at home, and been impressed that I was able to watch the monitor streams from my place of work.
Even my lowly PC and slow(ish) ISP allowed the system to work.
Now, I am also hosting a website on a virtual server hosted by 1&1, so clients are not slowed down by accesses to my own PC.
I would like to be able to view the output of a monitor at home, on the 1&1 website.
Has anybody done anything similar to this, and if so, how?
Remote Monitor Viewing
Re: Remote Monitor Viewing
im not sure how to do it exactly, somethign along the lines of embedding the stream into your site on 1&1, but you will of course still be limited by your home servers upload speeds.johno342 wrote:I have been happily using ZM for a couple of years now, running on my PC at home, and been impressed that I was able to watch the monitor streams from my place of work.
Even my lowly PC and slow(ish) ISP allowed the system to work.
Now, I am also hosting a website on a virtual server hosted by 1&1, so clients are not slowed down by accesses to my own PC.
I would like to be able to view the output of a monitor at home, on the 1&1 website.
Has anybody done anything similar to this, and if so, how?
________
Universal health warehouse
________
Dc Marijuana Dispensaries
Last edited by rDr4g0n on Mon Feb 14, 2011 4:43 pm, edited 2 times in total.
It sounds like you want to upload the live stream from your ZM box at home to your 1&1 account and view from there. I am probably misunderstanding something here, but I'm not seeing the advantage? If your ZM box is at home, your bandwidth is still limited by the upload limitations of your home ISP, and uploading from your ZM box to 1&1 and then loading pages from there just complicates things and provides an extra point of failure.
Why not just continue viewing your ZM box using your home IP address (or static, if you're lucky, or dynamic DNS)? If you are concerned about getting caught by your ISP for running a server/telemetry type application, you're probably more likely to get caught with the thing uploading to 1&1 all day and night than the limited times you connect from work and grab frames (unless you're on it all day anyway).
Also, if you upload to a hosted site, you have to be extremely careful about disk usage. At least at home, the worst thing is that PurgeWhenFull kicks in - you don't get large invoices for storage.
As noted, I'm probably missing something here...sorry!
Why not just continue viewing your ZM box using your home IP address (or static, if you're lucky, or dynamic DNS)? If you are concerned about getting caught by your ISP for running a server/telemetry type application, you're probably more likely to get caught with the thing uploading to 1&1 all day and night than the limited times you connect from work and grab frames (unless you're on it all day anyway).
Also, if you upload to a hosted site, you have to be extremely careful about disk usage. At least at home, the worst thing is that PurgeWhenFull kicks in - you don't get large invoices for storage.
As noted, I'm probably missing something here...sorry!
You make a valid point, and thank-you for posting.
The reason for using the 1&1 site is so that I can host several GB of video material, and not be compromised by the slower connection if I were to serve those files from home.
Obviously, when I want to show live video, the data has to originate from my home PC, as that is where the cameras are connected, hence my question!
The reason for using the 1&1 site is so that I can host several GB of video material, and not be compromised by the slower connection if I were to serve those files from home.
Obviously, when I want to show live video, the data has to originate from my home PC, as that is where the cameras are connected, hence my question!
Ah - so you want to upload events to the 1&1 site for *later* viewing/review. This makes more sense. 
You can set a filter that auto-generates a video file using ffmpeg whenever there's an event; then you want to upload video files to a directory on your 1&1 host. While I don't think ZM has that ability natively (at least not in 1.22), you could look into building a cron job or modifying zmfilter.pl to do the upload for you. I think there are posts here about doing that.
You still risk getting caught by your ISP - which I assume has TOS limitations on "serving" and what they call "telemetry" - basically periodic but consistent uploading of anything substantial. Video files are pretty substantial, even if you shrink them down to 160x120 size. Maybe you're lucky and your ISP doesn't have such terms, but they are all getting pretty wise to this stuff since bittorrent has been out for awhile.
You can set a filter that auto-generates a video file using ffmpeg whenever there's an event; then you want to upload video files to a directory on your 1&1 host. While I don't think ZM has that ability natively (at least not in 1.22), you could look into building a cron job or modifying zmfilter.pl to do the upload for you. I think there are posts here about doing that.
You still risk getting caught by your ISP - which I assume has TOS limitations on "serving" and what they call "telemetry" - basically periodic but consistent uploading of anything substantial. Video files are pretty substantial, even if you shrink them down to 160x120 size. Maybe you're lucky and your ISP doesn't have such terms, but they are all getting pretty wise to this stuff since bittorrent has been out for awhile.
The filters have native support for FTPing events to a remote location.
If you want more security and/or flexibility then take advantage of the scripting ability - the event ID can be passed to a script from which you can then upload the relevent files to your 1&1 server using whatever mechanism(s) your service supports.
Mathew
If you want more security and/or flexibility then take advantage of the scripting ability - the event ID can be passed to a script from which you can then upload the relevent files to your 1&1 server using whatever mechanism(s) your service supports.
Mathew
They can upload events as zip files, etc., but as of version 1.22 I believe they cannot natively upload *video* files generated by ffmpeg, like WMV or MOV files. If I'm wrong, let me know; I would really like to upload video files by checking a box and not having to write code to do it.MJN wrote:The filters have native support for FTPing events to a remote location.
Sorry to get OT a bit, but I wanted to clarify my earlier post.
OK, so I have nearly got something going now...
Essentially, the plan is to add a TCP Server to my zmc daemon, running on my home system, and emulate a 'remote monitor'
Local camera images get captured into the shared memory, as normal.
I configure my 1&1 server to have a normal 'remote monitor'
When the 1&1 server requires frames for the remote monitor, it connects to the zmc daemon running on my home system,
which then serves up frames using the normal mjpeg mechanisms.
I have got this working , but have a question regarding zmc
If zmc cannot get a frame from the remote system, then it simply disconnects, and then exits
What is the normal mechanism for getting zmc restarted?
Is this the job of the zmdc.pl script?
I would have thought that it was very likely that a remote monitor might not serve up frames for several seconds,
and would have expected zmc to stay in memory, and perform retries of some sort?
I appreciate that I could make the HTTP timeout as long as I like ( it is currently the default 2500ms),
but this seems like a sensible default point at which to do retries, rather than exit.
Or am I missing something here?!
Essentially, the plan is to add a TCP Server to my zmc daemon, running on my home system, and emulate a 'remote monitor'
Local camera images get captured into the shared memory, as normal.
I configure my 1&1 server to have a normal 'remote monitor'
When the 1&1 server requires frames for the remote monitor, it connects to the zmc daemon running on my home system,
which then serves up frames using the normal mjpeg mechanisms.
I have got this working
, but have a question regarding zmcIf zmc cannot get a frame from the remote system, then it simply disconnects, and then exits
What is the normal mechanism for getting zmc restarted?
Is this the job of the zmdc.pl script?
I would have thought that it was very likely that a remote monitor might not serve up frames for several seconds,
and would have expected zmc to stay in memory, and perform retries of some sort?
I appreciate that I could make the HTTP timeout as long as I like ( it is currently the default 2500ms),
but this seems like a sensible default point at which to do retries, rather than exit.
Or am I missing something here?!