we try recording over night, means starting 08:00 p.m.(20:00) till 05:00 a.m. As the result the configuration App (very. 1.2.1) creat two recording periods. 1. 00:00 till 05:00 a.m. 2. 20:00 till 24:00 The problem now: the audiomoth is starting with the first (1.) period. We are missing the time window of the 2. period (20:00 till 24:00) Before we have installed the Audiomoth update (Firmware version. 1.2.0) everything works fine, means starting time 20:00 till 05:00 a.m. without a break. What is going wrong after the Firmware update or what must be done from us?
I have installed version 1.2.5. The app will not recognise local time. It registers 1969 when I select local time. I have installed new batteries in the AudioMoth, although I did not need to. I have rebooted my computer (Windows 10). I did not have this issue with 1.2.2. I did not have any recordings when I deployed it for 12 hours last night (33 degrees F this morning. Older batteries at 4.0 V.) That has never happened but may be unrelated and perhaps I did not throw the switch all the way to custom.. Nevertheless, I just test recorded in default mode and it recorded fine but the date on four files was screwy. What is going on? Can I get back to the older configuration app? After this I flashed the unit and it now contains firmware version 1.3.0. I then deleted the configuration app from the computer and loaded it fresh. It still will not recognise the correct local time. I have some time constraints on what I am doing. This problem does not help. SOLUTION: Finally, I added the new version of the app to the Windows Defender firewall, and that appears to have resolved my issue. Interestingly, prior to this solution, when I reinstalled the app it would put the icon in the tray, but it would not automatically create a shortcut. Now it does, and all is well.