While I don't have an answer on how to fix this issue, I am encountering a similar problem with a batch of AudioMoths I just pulled out of the field. I programmed these AudioMoths to begin recording on July 15th, and record for 2 4-hour periods per day until battery failure. (~32 days) I programmed a batch of AudioMoths all at the same time, deployed them throughout June and early July and I am just starting to pick them up now. Of the 7 I have pulled from the field so far, only 2 recorded the expected amount of data, 1 recorded just 3 files (2 hours and 3 minutes worth of data) on July 15th, and the remaining 4 AudioMoths did not record anything at all. The only thing on each of those memory cards is the CONFIG text file. I am at a total loss on how this could have occurred, as the batteries of the ones that failed to record anything or only recorded for 2 hours are all still apparently full (>4.9V). When I plugged an AudioMoth (the one that recorded for 2 hours and then stopped) into the computer I did notice something funky going on with the clock though. The date appears to be stuck on July 15th and the time is moving extremely slowly. I have attached a 30 second video clip of what the Configuration App looks like when I plug one of these AudioMoths in. For reference the local time this clip was recorded should read (16:14:02 11/9/2020 UTC-7).

Hey everyone, I have been waiting for this update to the configuration app as well. We have about 250 AudioMoths that we will be deploying at more than 120 locations across roughly 10,000km2 this spring, and having the ability to program them to all turn on on the same day would make subsequent data analysis exponentially cleaner. It generally takes us well over a month to reach every site, and by then the batteries on the first AudioMoths deployed are dead (running 8 hrs/day = mean of 31.7 days). If I can sync them all up, I won't have to model the temporal variation between sites, and additionally I could deploy 2 AudioMoths per site, with one scheduled to begin data collection as the first one died, effectively resulting in a continuous 2 month window of data collection. While I am not super familiar with the programming language or code used to build the configuration app, I can learn it and run the code that Alex and his team have provided here and on GitHub if necessary (Which has been extremely helpful and generous by the way). I just wanted to check and see if I should go that route, or if there may be an update coming out soon that will will include this feature. Thank you for all you do! Trent

Thank you Alex, I had the exact same question after deploying over 150 AudioMoths this summer. I did a terrible job of calculating battery life, and learned that even with lithium batteries the Audiomoths were dying in the field months before I anticipated going back to them. This feature should really help address that issue, because we could place multiple AudioMoths in the same location and have them turn on in sequence as the batteries in the preceeding AudioMoth die. It will also allow field researchers to deploy many AudioMoths over several weeks or more in a more logistically feasible manner and then have data collection begin simultaneously. On a related note, is there a different way to display battery usage, or somehow estimate how long batteries will last given a particular configuration? I appreciate the information regarding the number of mAh per day, but I don't really know how to translate that into something that corresponds with how many days I can expect with 3 AA batteries. In my situation I calculated 3 * 3000mAh (size of each Lithium Ion battery) = 9000 mAh. I thought this might give me something approaching 100 days at 8 hours of recording per day, but all of my AudioMoths died around 30-33 days. I am assuming that there must be more to that calculation than what I did, but I could not find any information on how to calculate battery life expectancy at a given use rate.

Thank you Dr. Rogers, It looks like I am running Version 1.2.1 ; Electron Version 3.0.0 ; AudioMoth-Hid module 1.0.19. I have been using the local time button in the configuration app (which is a really nice addition by the way), but I had turned that off and gone back to UTC because I thought that might be what was causing problem. That didn't seem to make a difference. The text fields for setting up a new recording period are the local times. I must have turned off the local time button after entering the time, (I had pressed add recording period before turning off local time) . The corresponding time in UTC is listed over in the recording period window.