In addition to the installation instructions and the firmware binary itself, it would be a good idea to include a changelog file in your firmware packages.

It would be good if there were an option to have saves to FTP automatically create subfolders, with, say, a yyyy-mm-dd format... or better yet, user specified format based on common naming scripts ie: "your text here"&yyyy-mm-dd&"texh here if you wanted"

Oh, and you might want to add the info regarding the sensitivity level to the FAQ, it would help a lot, in particular
"1. level 1: It will trigger motion when there is 0.5% of the video area with motion object.
2. level 50: It will trigger motion when there is 10% of the video area with motion object."

Currently the FAQ suggests a setting in the range of 10 - 40 for daytime, but 1-20 for nighttime... quite the opposite of what you are suggesting here.

I'm not getting any e-mails - not even for replies to topics I created

I'm getting a lot of recording going on even at 50 during the night on my camera. The only "motion" I can see in the videos, for the most part, is shifting light levels from one frame to the next... which I don't think is really changes in the visible light out there, as it really does appear to abruptly shift from one frame to the next.

What would be useful is if there was also an ability to set a threshold level for how many frames in a row the motion is detected over.... I believe that is what some of the more sophisticated motion detection algorithms do.

Regards,
Eric

Well then there must be something wrong with my camera... I have the motion sensitivity turned all the way down to 40 and I am still getting false hits during broad daylight. Nothing is moving in the video - except in the areas that I excluded using the Windows client software. Not too many false hits at 40, trying 42 now... at 30 it was constantly going off. At nighttime it is useless... even at 50 it is constantly detecting motion.

Now when I first got it (a few days ago) I didn't seem to be getting this many hits... I upgraded the firmware the other day though... so while my suspicion is that somehow the excluded areas are not being excluded, maybe it is something with the new firmware?

While you're working on that, could you also please allow users to use a longer file path in the ftp field? Right now it is quite constrained... somewhere around 32 characters max

I need to be able to mask out a roadway from the motion detection. I can do this in the windows client, but I think those settings get overwritten (going back to the default of detection for the whole area) every time I do something in the mobile app.

The mobile app needs to, at the very least, recognize when an area has been masked off and preserve that and, ideally, allow for editing that masked area.