Original Message - [10/25/2009 - 08:21 PM]Original Message - [10/25/2009 - 06:42 PM]Original Message - [10/24/2009 - 03:55 PM]
Ok, I'm making some progress BUT there is still a problem. Perhaps this is a bug.
It appears that both LocalSave and FTP are supposed to work the same.
1) Images are saved every INTERVAL TIME (either locally or by FTP)
2) The image with the most motion is supposed to be saved or FTP'd
3) If there is no motion, nothing is saved or FTP'd
Is that how it's supposed to work?
3) Emails is still confusing.
I have gotten emails to be sent with LocalSave but NOT with FTP. Both have the same settings and were tested seperately. Both work with TEST email. However...
1) Emails configured in the LocalSave are sent everytime an image is saved, which is what I like. BUT don't seem to follow the "Email only Every X hours". For instance, I have that setting to: Email only every 1 hours. But if my testing interval is 5 minutes, an email is sent every 5 minutes. How is that setting supposed to work?
2) Emails configured in FTP motion detect are NEVER sent. It does send the test email so I know it's configured properly. Why would emails be sent for LocalSave but not using the FTP settings? Keep in mind, I have tested each of these, with the other turned off. FTP motion detection never sends emails, even though it will FTP an image.
Finally the bug. The saved or FTP'd images are supposed to be the image with the most movement. However, I'm finding that's not the case. In fact, some images that are sent, are from previous intervals.
As a test, I configured the system to send various images, so I knew which image was from which interval. Then after changing the intervals a few times and going back to a very short interval, I found that the images that were being saved were from much early intervals.
There needs to be a way to flush out the image storage areas, when the server is reconfigured for a new interval, to avoid sending earlier captured images.
Ok, I'm making some progress BUT there is still a problem. Perhaps this is a bug.
It appears that both LocalSave and FTP are supposed to work the same. I base this on how I find it to work. So I'm asking for confirmation on this.
1) No images are saved or FTP'd curing the idle time specified
2) Images are saved every INTERVAL TIME (either locally or by FTP)
3) The image with the most motion is supposed to be saved or FTP'd
4) If there is no motion, nothing is saved or FTP'd
Is that how it's supposed to work?
5) Emails is still confusing and not working consistently.
I have gotten emails to be sent with LocalSave but NOT with FTP. Both have the same settings and were tested seperately. Both work with TEST email. However...
1) Emails configured in the LocalSave are sent everytime an image is saved, which is what I like. BUT don't seem to follow the "Email only Every X hours". For instance, I have that setting to: Email only every 1 hours. But if my testing interval is 5 minutes, an email is sent every 5 minutes. How is that setting supposed to work?
2) Emails configured in FTP motion detect are NEVER sent. It does send the test email so I know it's configured properly. Why would emails be sent for LocalSave but not using the FTP settings? Keep in mind, I have tested each of these, with the other turned off. FTP motion detection never sends emails, even though it will FTP an image.
Finally the bug. The saved or FTP'd images are supposed to be the image with the most movement. However, I'm finding that's not the case. In fact, some images that are sent, are from previous intervals.
As a test, I configured the system to send various images, so I knew which image was from which interval. Then after changing the intervals a few times and going back to a very short interval, I found that the images that were being saved were from much early intervals.
There needs to be a way to flush out the image storage areas, when the server is reconfigured for a new interval, to avoid sending earlier captured images.
Original Message - [10/24/2009 - 03:55 PM]
Ok, I'm making some progress BUT there is still a problem. Perhaps this is a bug.
It appears that both LocalSave and FTP are supposed to work the same.
1) Images are saved every INTERVAL TIME (either locally or by FTP)
2) The image with the most motion is supposed to be saved or FTP'd
3) If there is no motion, nothing is saved or FTP'd
Is that how it's supposed to work?
3) Emails is still confusing.
I have gotten emails to be sent with LocalSave but NOT with FTP. Both have the same settings and were tested seperately. Both work with TEST email. However...
1) Emails configured in the LocalSave are sent everytime an image is saved, which is what I like. BUT don't seem to follow the "Email only Every X hours". For instance, I have that setting to: Email only every 1 hours. But if my testing interval is 5 minutes, an email is sent every 5 minutes. How is that setting supposed to work?
2) Emails configured in FTP motion detect are NEVER sent. It does send the test email so I know it's configured properly. Why would emails be sent for LocalSave but not using the FTP settings? Keep in mind, I have tested each of these, with the other turned off. FTP motion detection never sends emails, even though it will FTP an image.
Finally the bug. The saved or FTP'd images are supposed to be the image with the most movement. However, I'm finding that's not the case. In fact, some images that are sent, are from previous intervals.
As a test, I configured the system to send various images, so I knew which image was from which interval. Then after changing the intervals a few times and going back to a very short interval, I found that the images that were being saved were from much early intervals.
There needs to be a way to flush out the image storage areas, when the server is reconfigured for a new interval, to avoid sending earlier captured images.
Ok, I'm making some progress BUT there is still a problem. Perhaps this is a bug.
It appears that both LocalSave and FTP are supposed to work the same. I base this on how I find it to work. So I'm asking for confirmation on this.
1) No images are saved or FTP'd during the idle time specified
2) Images are saved every INTERVAL TIME (either locally or by FTP)
3) The image with the most motion is supposed to be saved or FTP'd
4) If there is no motion, nothing is saved or FTP'd
Is that how it's supposed to work?
5) Emails is still confusing and not working consistently.
I have gotten emails to be sent with LocalSave but NOT with FTP. Both have the same settings and were tested seperately. Both work with TEST email. However...
1) Emails configured in the LocalSave are sent everytime an image is saved, which is what I like. BUT don't seem to follow the "Email only Every X hours". For instance, I have that setting to: Email only every 1 hours. But if my testing interval is 5 minutes, an email is sent every 5 minutes. How is that setting supposed to work?
2) Emails configured in FTP motion detect are NEVER sent. It does send the test email so I know it's configured properly. Why would emails be sent for LocalSave but not using the FTP settings? Keep in mind, I have tested each of these, with the other turned off. FTP motion detection never sends emails, even though it will FTP an image.
Finally the bug. The saved or FTP'd images are supposed to be the image with the most movement. However, I'm finding that's not the case. In fact, some images that are sent, are from previous intervals.
As a test, I configured the system to send various images, so I knew which image was from which interval. Then after changing the intervals a few times and going back to a very short interval, I found that the images that were being saved were from much early intervals.
There needs to be a way to flush out the image storage areas, when the server is reconfigured for a new interval, to avoid sending earlier captured images.
Ok, I'm making some progress BUT there is still a problem. Perhaps this is a bug.
It appears that both LocalSave and FTP are supposed to work the same. I base this on how I find it to work. So I'm asking for confirmation on this.
I have gotten emails to be sent with LocalSave but NOT with FTP. Both have the same settings and were tested seperately. Both work with TEST email. However...
1) Emails configured in the LocalSave are sent everytime an image is saved, which is what I like. BUT don't seem to follow the "Email only Every X hours". For instance, I have that setting to: Email only every 1 hours. But if my testing interval is 5 minutes, an email is sent every 5 minutes. How is that setting supposed to work?
2) Emails configured in FTP motion detect are NEVER sent. It does send the test email so I know it's configured properly. Why would emails be sent for LocalSave but not using the FTP settings? Keep in mind, I have tested each of these, with the other turned off. FTP motion detection never sends emails, even though it will FTP an image.
. The saved or FTP'd images are supposed to be the image with the most movement. However, I'm finding that's not the case. In fact, some images that are sent, are from previous intervals.
As a test, I configured the system to send various images, so I knew which image was from which interval. Then after changing the intervals a few times and going back to a very short interval, I found that the images that were being saved were from much early intervals.
There needs to be a way to flush out the image storage areas, when the server is reconfigured for a new interval, to avoid sending earlier captured images.