To see this working, head to your live site.

Configuration app will not pass through Windows 10 firewall

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?

21 comments

21 Comments

Alex Rogers

Mar 01, 2020

So, going back to your computer. Can you post a screenshot that illustrates what is preventing you from running the Config App there.

Russ Wigh

Mar 01, 2020

Replying to

I'm happy to do that. Simply put, the window on-screen with the bar showing the installation process never got past half way, and just stayed there as long I as I did not click it off. But first, let me go back and restore the operating system to 4 or 5 days ago when things appeared to be working. This is about that last card I can play. But if this doesn't work and you have a workaround I still have access to the installed app on my wife's account on this computer, and my account on her computer.

Russ Wigh

Mar 01, 2020

Replying to

The store feature has included the configuration app on my user page, but when I connect a device with batteries and and the grey time goes to black the time reads: 00:44:XX, 02/01/1970. When I click on local time it becomes 19:45:XX, 01/01/1970. The correct time here is 14:16. Can I not configure the app, then configure the Audiomoth since now the times are correct and then install the batteries before disconnecting?

I will read the link you sent, but I am spent for the day on this. By-the-way I went through the process with no batteries. The configuration bar blinked like it was working - accepting the instructions - then I installed the batteries, disconnected and and switched it to custom. I will leave that on my desk, with both green and red LEDs blinking and see if it switches to record at 19:00 this evening.

Russ Wigh

Mar 01, 2020

Replying to

Alex

I was reading back over others' issue and came across a similar issue from June 2019. Your instructions to him were to click on the configure button and the correct time would come up!! I tried it and hopefully programmed all of my units. I have switched to custom and they are all blinking green! I programmed them for 19:00 to 06:00. Those are the times I need on an ongoing basis this week. Over here we have an expression 'If it ain't broke don't fix it." I am willing to wait out the next four hours to see if they all switch to record. Also, when I exit the configuration app and brought it back up the correct time was still there!!! Is this the answer?

Alex Rogers

Mar 01, 2020

Great. This means the configuration app and the AudioMoth are working as intended. There is a very comprehensive guide here on how to use them here - https://github.com/rhine3/audiomoth-guide/blob/master/guide.md

Alex Rogers

Mar 01, 2020

The local time option just applies the local time zone offset (-5 UTC in your case) to the time returned from the device. The only way to set the time is to press 'Configure AudioMoth'. Are you sure this isn't working as this is quite a strange bug if not; the app is clearly able to communicate with the AudioMoth and it is responding to the other messages as expected. Can you try the following:

1) Remove batteries from the AudioMoth and leave unconnected.

2) Close and re-open the Config App. Confirm the version of the app in the 'Help' menu.

3) Plug in the AudioMoth. The time should go black and start counting up from 00:00:00 01/01/1970. Can you confirm the version number reported on the front page of the app.

4) Click the 'Configure AudioMoth' butt