I am planning on using the 1.2.0 version of AudioMoth with a Sennheiser ME62 mounted in a parabolic dish to record migrants at night. The microphone - a condenser - is powered by a standard alkaline 1.5v AA battery when not using phantom, not PIP. Is there any reason this should not work? Haven't tried it yet. Soldering iron crapped out and waiting on a new one to arrive. Thanks.

Ever since a configuration upgrade my recorders are skipping every third file programmed to be recorded. I have had a discussion with others on the device support for the past two days and we are making no headway. I have run numerous tests using the settings 0 sleep, and 900s record, and the only time all the files were recorded, even with older batteries, was when I neglected to change the record-sleep period from the default 5s,55s. Then all the files recorded. Is there s fix for this or can we switch back to a previous configuration file? This one is not working properly.. And yes, I unchecked the box for low voltage cut-off.

First, I posted a picture of this small, inexpensive box on December 28, 2019. Briefly, they cost about US$2-5.00. Made in China and available on eBay. Convoluted foam inside top and bottom. I drilled out a hole in the top 7/16 inches and installed a 1/2 inch rubber grommet. Inside the lid I taped part of the original plastic bag all the way around. I placed the microphone directly under the hole in the case. The grommet does two things; secure the AudioMoth in place between the foam layers, and provide just enough of a raised 'bump' to ward off drips of rain that might otherwise ingress. They may help with deflecting wind. I did not have much rumble, but my attention was fixed on owl vocalizations, not wind. I deployed 4 AudioMoths in these boxes over 1138 hours of night recording. I used 14 inch cable ties to secure the unit to a small tree by the tabs, and wrapped the boxes in camouflage stretch tape, available on Amazon. Some deployments were in state parks filled with curious humans, others in remote areas filled with curious wildlife sniffing and poking. I never lost a box or a unit, and none every failed, or came loose from a secured location. I brought the last unit in this morning; it was out for 5 nights, recording 10 hours a night, one of which featured a major storm which dumped 2.5 to 3.5 inches of rain. The unit was completely dry, all 200 fifteen minute recordings were clear, and I did not find the screech-owls I was searching for.

The whole sordid story of my efforts to restore the configuration app to the correct time are below, including Alex Rogers staying with me during the six hour ordeal. The bottom line is this: If your configuration app consistently shows the year 1970 both in UTC time and local time, don't do what I did and try to reload the app. That may not work, and repeated efforts in Windows 10 are likely to block the app from installing at all. When you program the app and then plug in the device, simply click the green configuration bar and the correct time will come up and register in the the device. I did this with four Moths and deployed two last night. All are working fine.

I am having a fit. I has version 1.2.5 up and working yesterday by adding the app to the Window Firewall. Now nothing. I have tried to disable the firewall and reload the app. When I try to check local time on the app I am getting 1969 as the year and the time as no relation to reality. Is there anyone who can help me with this problem?

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.

Small plastic boxes advertised as rainproof are $2.00 to $5.00 on eBay. They consist of convoluted foam top and bottom and four tabs for locking the box as well as two small loops on one end for mounting. They are shown elsewhere on this forum as well. The AudioMoth fits nicely without taking any foam out except for porting it to expose the microphone. I drilled out a .5 inch hole (12.7mm) in the lid above the microphone and inserted a a rubber grommet with a .5 inch slot diameter. (The picture I have included shows a smaller .375 inch diameter grommet which I changed out for slightly more exposure.) I have already tested the Moth wrapped in the pink plastic bag in which it came, with only modest attenuation of the signal. I have also included five test I ran for interested parties to compare. The profile is nice and there is no need to glue anything. Simply place the plastic over the microphone before closing the lid. The pressure of the foam and the inside of the grommet will keep the Moth from moving. Apparently I can add only one file. This one is with plastic in place and the foam ported. I am about 7-8 meters away.

New data cable, reformatted card, computer recognises connection, configuration okay. Followed initial setup several times. Will NOT record in either custom or default settings. Now what??