My solution to this problem was to use a longer sleep time. I think I just went to 60 seconds, and have not had any problems since.

Just tried it by pressing the the socket against the AudioMoth contacts. Should have done this and then posted the results, not the question. Works great.

Mouser Electronics. I believe they are in Texas, but the jack will not be back in stock until early September. They are about 1/2 the price of GroupGets - which shorted me one on my original order.

John The only think I can further suggest is to be sure you have flashed to the latest firm ware upgrade, 5.XX. Not sure where they are now, my units are at 5.0. Fast and simple download if you have not. If you have already, try it again. I cannot speak to lithium batteries. I have had trouble with them in other applications, so I stick to branded alkaline AAs. If this does not work for you I would have two or three suggestions: Go back to GroupGets or Labmaker if you bought them in Europe, and see if others have described the same problem to them. You could also Google the problem, which I did as a last resort on my local time issue, and got an answer. Another thought would be to see if your seller can tell you the name of a university department which has purchased a good many of them, and may have the expertise to work through your problem. Finally, you could email the guys in England who designed them and describe the issue. All this said, all my units are version 1.1.0. I see that 1.2.0 is now available through both campaign agents and I do not know what differences there might be other than an upgraded microphone.

@john Okay, I think you will find that works. I have been there. So for anyone else on this thread a word about editors for endless numbers of AudioMoth files. I have used Audacity for years and it is my goto editor. For AudioMoth I have iZotope RX7, but they make an Elements or Lite version which can be had for as little as $130 as I recall. iZotope RX7 will support up to 16 open files at time, which makes the analysis process pretty painless. It also presents a clearer spectrogram than Audacity. A second hairy problem I have run into where I can save you hours of frustration. In the configuration software it sometimes will not give me the correct local time. If you have this problem don't panic. It took me two solid days to get an answer. Simply click the configuration bar the the right time should show up.

The problem is 0 seconds between files. Change that back to 5 sec. and you will be fine. Also 10 or 15 minute files allow you to see slightly more detail in the spectrogram in your editor.

Thanks Michael. My test ran smoothly as well.

Thanks for keeping me in the loop. I will run a three day test myself using a similar configuration.

Michael, my issue is resolved by changing the sleep schedule to 5 seconds, but I am concerned about yours as well since I leave mine in the field for multiple nights. I can't help but think yours is a configuration issue as well. Do you mind reporting your problem on the configuration forum. I got an answer fairly quickly from one of the administrators. I will follow your progress there.

Thank you, Andy I ran a test last night at 5 sec sleep and all is well. In former configurations - over 1,000 hours this did not happen at 0 sec.

Michael What version of the configuration app are you currently running? I was running 1.3.0. I went in and found the latest is 1.3.6 and downloaded that one. I am going to try again and see it the bug we are experiencing has been fixed

New batteries made no difference. Once again every third file did not record. This is a problem I need to solve. I am beginning the second year of a project. Michael, I don't see my original post to the configuration support forum. I will try there again, and perhaps someone has an answer. I see that the administrators have been active on that page.

I went into the Configuration Support forum and asked this same question. We cannot be the only ones with the problem. I do remember - vaguely - that there is a way to go back and use a previous configuration app, pre-upgrade. As I mentioned above, I installed new Duracell alkaline batteries to see if additional voltage makes a difference. That test should finish in about 2-1/2 hours. I will post.

I posted to device support that my units are skipping files they have been programmed to record. In a six hour test session last night for intervals of 0, 900 I should have had 32, 15 minute files. The unit recorded only 22, skipping every third recording session. This did not happen before the most recent upgrade. The batteries read 3.8 volts to start, and I unchecked the low voltage box. Others are experiencing similar issues. I am going to try again with fresh batteries. If that does not work is there anyway to return to a previous version of the configuration app?

I ran two more tests and both failed. I recorded from 1000 to 0600 last night and the recorder skipped every third session, 10 files??? It makes no sense. I have never had to replace batteries that clearly had sufficient charge, but I will try that before bugging the administrators.

Hi Michael, I let my test finish. I forgot to reconfigure for each recording segment and had the default 55 seconds and 5 secs paused. I had all 180 files in sequence. I an running it again the rest of the day to verify. As to your problem of the recorder stopping altogether, I'm no help here. Is it possible you have something on the Advanced Settings configuration page checked such as amplitude threshold?

Thanks. I did not experience a complete stop. Mine might have been okay for the better part of the night and then stopped toward dawn for 30 or 45 minutes, with one or more final segments recorded. I was just writing a friend. I will wait to hear back from you.

I think the answer is on the first page of the configuration app. At the bottom uncheck the box for "Enable Low-voltage Cutoff. In my first response to this issue I suggested new batteries. I did not make that change. I have noticed when I have come in from the field that when I measure the remaining voltage in the recorders with my own testing equipment, I can get one reading, and some minutes later it is higher. That is consistent across all my units. Last night I noticed in the configuration app that my batteries were at 4.0 volts. During recording a segment they apparently dropped below that level and the next 15 minute segment was not recorded. Then the unit recovered, and recording proceeded. I typically let them run down to 3.5 volts before discarding the batteries unless I expect them to be deployed for 5-7 nights. This action is not well described in the start-up of the configuration guide nor is there any indication I have found what low voltage level triggers the cut-off. I is pretty obviusly 4.0 volts.Perhaps I missed these points somewhere. In any event I made these changes to my test unit. It is about half-way through the exercise and it has recorded all 6 - 15 minute segments flawlessly. Hope this helps.

Looking for an answer to the same problem. I have been recording in 15 minute segments (900) with '0' sleep (still 1 second) for about a year. I did not experience this problem until the first configuration upgrade as I recall. Last night the same problem again with one unit I was playing with. I just deployed that one again in the garden with batteries reading 4.0v. I have easily recorded all night long in the past with less than 4.0 volts. This could be a serious issue. I hope the administrators are monitoring this thread. I will put in fresh batteries and reconfigure to see if that makes a difference. I will report back. This is a bummer!

I got caught again, two inches (5cm) of hard rain. This time two of the units in their cases were pointing up at maybe 30º. Water did get past the plastic barrier in one case but was largely absorbed by the eggshell foam on top of the Moth. The surface of the Moth was damp, and it was 24 hours before I picked them up. There was no damage, and the recordings were clear and intact. Those units which were mounted vertically in their cases were completely dry.