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?
Support Forum
Get technical support and coordinate group purchasing
Can you post a screenshot and describe what you mean by 'Now nothing'. It sounds like the app is starting, the config app is showing 0 time, which is 00:00 1st Jan 1970, and when you switch to local time this is showing up as 1969 as you are in a timezone west of 0 degrees longitude. This all sounds fine. Is the app not talking to the AudioMoth device?
Alex
I will get you a screenshot, but to add to the problem one of the three units I received today will not even be recognized by the configuration app at all, or the other two apps; flash and time. The other three Moths at least cause the configuration app to 'wake' if you will, but the times are way off. All batteries are fresh today. It will not work on my wife's computer either. The problem is that even with the configuration app in a folder, and that path added to the Windows Firewall list of approved apps I get the same Firewall warning. and the configuration app will not display the correct time. I have search for Windows Defender issues on the Web, and nothing similar has been reported.
I had this problem a few days ago and solved it by adding the configuration app to the firewall list. Now that process does not work even when I turn the firewall off.
Which screenshot would you like?
Hi Russ, Can you confirm where these AudioMoth came from. The time displayed is the time on the AudioMoth. This will start at 00:00 1st Jan 1970 when you first put the batteries in or plug in the USB cable. The time is only set when you press the 'Configure AudioMoth' button in the Config App. Is this not happening? Can you post a screenshot of the firewall warning and confirm what version of Windows you are using. Alex
Shot is below. Hope it comes through okay. I can tell Windows Defender to let it through, but that is not helping. I have tried that numerous times.
I am using Windows 10 Home. All four units came from GroupGets. I bought 1 from Campaign 8 on 2 December and it worked flawlessly up until the switch to 1.2.5 and upgraded the firmware to 1.3.0. The other three are from Campaign 9 and they were received today. I had this same issue earlier this week with the first unit, but I resolved it by adding it to the Windows firewall approved app list and that worked. Now it does not.
The 'dead' unit was a battery issue, now resolved.
Great. So all the devices are working fine and the only issue is the Config App. Is that correct? Can you try the earlier version of the app from here - https://github.com/OpenAcousticDevices/AudioMoth-Configuration-App/releases/download/1.2.3/AudioMothConfigurationAppSetup1.2.3.exe
That did not work either. I had earlier tried 1.2.2 from that same page.
Last night, regardless of how many times I tried, the app would not recognize any of my Moths with the correct time, although the app did recognize that they were plugged in. I cleared everything out to start fresh. This morning the app will not even load on the computer. Now I have no app. I have checked with my provider, Comcast, and they have no problem in my area.
I'm not sure I understand what you mean by 'the app would not recognize any of my Moths with the correct time, although the app did recognize that they were plugged in'.
When you launch the Config App the first time the time should show '00:00:00 01/01/1970 UTC' and will are greyed out as no AudioMoth is detected.
When you then plug in the AudioMoth it will detect the device, show you the serial number of the device, and the time will show the current time on the device. If it has just been plugged in and has no batteries, the time will start from '00:00:00 01/01/1970' and will increment each second. The 'Configure AudioMoth' button will also now be enabled.
Now if you click 'Configure AudioMoth' the current configuration will be sent to the device, and the time will updated to the time on your computer.
Can you confirm which of these stages is not working as described above?
Well first, I cannot reload the app on the computer at all. So I can't test that this morning.
Last evening when I plugged any of the four Moths in with the configuration screen up, the tie would go from grey to black indicating a connection. I could move around the app and set up the configuration I wanted before I plugged in the Moth. The time never read the correct UTC time, and when I check local time from the menu it was always wrong.
I have disabled the firewall, and disabled something called Windows Defender Smartscreen which was theoretically blocking the app. nothing works. As I said above, the configuration app will no longer even load on my computer. I will now turn off my computer and reboot it to see it that clears whatever is blocking the app from even loading on the machine.reboot my computer. I will let you know.
I have reboot my computer and the app will no longer even load. Now issue number one.
I have returned to my wife's computer where I still have the configuration app, and plugged in a device and I STILL do not get the proper time. The app appears not to be reading the correct time from the computer.
The correct time will only appear when you click 'Configure AudioMoth'. Is the problem that even after clicking 'Configure AudioMoth' the correct time did not appear?
That is correct. I have the configuration app on my wife's computer and now on my computer under her username. When I plug a device in the gray time goes to black. The UTC time reads 16:39 and ticks off the seconds. When I check the drop-down menu for local time I get 11:XX. It is 09:15 here. If there is even a MANUAL way to set these times it is a band-aid, but at least I can theoretically move on.
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' button. The time will update to the current time in UTC.
Version: 1.2.5
Electron version 6.0.1
Audiomoth HD module 2.0.2
Firmware 1.3.0
The current time on the configuration app - on my wife's page is 18:++ hours
This is working as you instructed. What is the next step?
I need to add the time is 18:12 and seconds at the moment, the date is 1/3/2020. That is correct.
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
So, going back to your computer. Can you post a screenshot that illustrates what is preventing you from running the Config App there.
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.
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.
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?