Does anyone else think that this update was released that included portions of older/retired code?
So what sounds more believable - That this reversion to the old and inferior motion zone layout was intentional or that this was a pitiful case of source code mismanagement? Oh, of course, the release notes will confirm if this was intentional, right?
If you were to review your config.backup, the "MotionDetectWindow" section contains 18 rows of "Region" values that represent the detection grid. I would assume that this did not change from the values before the firmware update. I sure wouldn't mess with settings on this "new" Zone 1/2/3 layout which probably will update that linear grid with new values based on what - a predetermined pattern?
Sadly I am not able to look at my Main computer atm for looking over the 2 config files I do know that looking at the new FW there is on my camera anyway 7575 lines in text format.. Again this computer I am using right now has limited software in it so I didn't look over the other CGI command that I would need to copy into a word doc so the text CGI is the one I am using right now.. Looking for the Motion Detection window area is strange if I am not reading this wrong it looks like there is only 1 region; in there it has 18 numbers yet only last 4 have any value also the Thrush and Sens are both set to 100 and again getting loads of false alarms compared to last FW...
Also there are some strange things in this config that I don't remember seeing in the other and it might have been there but I think it would have stood out then like it did this time..
Right now I am replacing the Power Supply in my main computer from a 750 to an 850 so I will have to look over the 2 config files and see if it was present or not last time..
Oh great - you're seeing more false positives now with the update.
Here's a shortcut to viewing your current 18x22 motion detection blocks: <ip_addr>/cgi-bin/configManager.cgi?action=getConfig&name=MotionDetect[0].MotionDetectWindow[0]
In case you are interested in the technical bits, each of the 18 regions (rows), are listed with an integer. That integer, converted to binary, represents if each block is on or off. There are 22 blocks in each row, so if the entire row was highlighted in blue, the binary representation is 1111111111111111111111 and that will convert to 4194303 as shown in the config. An empty/unhighlighted row is just 0.
So why bother with this technical explanation? Just to find out if the new firmware update also applied a new default motion detect mask based on the 3 zones or if it left what you had there before. Since you can no longer see the original detection blocks with the app, looking at the config is the only way to know what you have.
Still wondering if this change was intentional or not. Has anyone submitted a ticket to find out?
I didn't do a Ticket but I did have some contact with my Amcrest Contact and was just before he had to go home for the day last asked me to send him a Screen shot of current Zone setup so he could contact the R&D and find out if it was meant to roll out this way again..
Sadly it isn't as cut and dry these days with Support... Seeing this is a Smart Home Product my contact isn't part of that department and from what I am finding out is unclear at times at when or what is rolling out.. The last FW update for the AD110 he didn't even know one had rolled out and was told when I first said I made the update in FW that there wasn't one... After some time finding out that I was right there was a new FW.. It looks like this time he was aware of the update and is trying to clear up some questions about this update and changes in things.. One Question I also asked is why did someone that had the update have a faster change in Grid then after I did the update and did 2 reboots and a Reset with still having the old Grid looking setup until I left home for a couple of hours and returned to find that sure enough it had changed back to the Legacy looking setup.. I don't like it myself but time will tell.. Back to getting 100 alerts again for nothing but cars driving by and things I don't care about again and will just end up turning off motion alerts to correct this.. Sadly this means that I will miss or did in the past some Button presses as well. Some times I wouldn't get a Notice on first push wasn't until after a second without motion enabled..
Here is the Result from the CGI on my Motion and by the way the little bar on the left I have 1 spot to the bottom and in my mind in no way should be 100 100 but sadly as someone not long ago said IT is what it is...
Revo, your current motion detection window has only the lowest 4 rows highlighted as specified with the 523776 value. Converted to binary, the following 4x22 blocks are enabled for motion detection...
0001111111111000000000
0001111111111000000000
0001111111111000000000
0001111111111000000000
Is that pattern that you had clicked ON in blue BEFORE the update? Or maybe you already clicked on the new zone pattern trying to reduce the false alerts and this is the result?
As to the range slider on the left, assuming that represents the same relative value as the motion range (1-6) value before the update, that value is stored in an unexpected place in the config... _Pir_[0].DutyCycle=xx where xx scales from 0 to 100.
BTW - The Windows 10 calculator has a programmer mode that can convert integer values to binary. Just pad the result to the left with zeroes to equal 22 bits.
Yes that is how I had it set up but odd thing is I did a Reset after the FW update so that shouldn't show the last Grid results humm Unless the Reset failed and acted as a Reboot but that is strange it still shows the Grid from before FW update
I wonder now seeing I had to do 2 Resets on the last one to get rid of the Purple color I was on at that time.. Since the Purple I have had Green as well but only 1 Reset was needed to get rid of that and I didn't make any Color changes in any view or recording method so that is strange..
Not heard of anyone else having to get rid of Smurfs and Shreks invading their camera, requiring several resets to shoo away.
I'd ask Amcrest for a new AD110 in exchange for all the dedicated support you give. There hasn't been anyone from Amcrest post in this forum for a long time that I can tell.
when i saw the firmware has reverted back to the original motion detection zone view, i waited a few minutes for the front door view to show up. since i can't see view the front door view after several minutes, i simply backed out of the zone view so i don't alter any of the previous motion detection settings i have before the firmware update. hence perhaps i'm not getting any false alert at this time.
Assuming that your SmartHome app did not get updated and is still at V3.5, then how could the "new" 3 Zone UI appear in the app after a firmware update? This code must have been in the app all along and something in the firmware update enabled it instead of the grid mode.
This could also explain how Revo still saw the 18x22 grid after the firmware update. His app may not have read the switch that turned on the alternate 3Z universe yet.
So if anyone has a config.backup from before the update and can compare it after an update, it might reveal what this switch is.
Also, it would be interesting to confirm if "RecordLatch" is now "30" after the update (It was 10). If so, this would correspond to the firmware update note that "push notifications for MD will wait 30 seconds between events...". That's a welcome change, but I would like to make it even longer.
Last edited by GaryOkie on Thu Sep 17, 2020 2:23 pm, edited 1 time in total.
