I encountered a possible bug while using the chime feature of the Rainforest Connection "Companion" app to set the time on an AudioMoth today.
I had just configured the AudioMoth a couple hours before, but it was jostled and lost its set time. I used the app to set the time. After that, I changed the AudioMoth to USB/OFF mode and plugged it into my laptop to check that the time was set correctly. The config app showed that the time was late by 2 hours (displaying 17:44 UTC instead of 19:44 UTC). I am in Eastern timezone, UTC-4:00. I tested the AudioMoth by removing the batteries and attempting to use the app again, and this behavior happened again once or twice, then stopped happening.
Subsequently I have reproduced this problem and gotten a variety of incorrect times, including roughly 2 min, 20 min, 35 min, 40 min, more than an hour, etc.
Has anyone encountered this or could think of a reason it could be happening? One possible source could be some very high frequency sound in our lab space aliasing down into the audible frequencies and messing with the app chime.
Hi Tessa, The fix for the time bug will be coming out on the Google Play Store over the next few hours. Alex
Hi Tessa, Yes, we reproduced this. The time it sets seems to be the time that the app is opened, rather than the time you press the button. That will explain the increasing offset. The workflow is also quite complicated in that it isn't really described in the app what the tone is doing, or that you need to switch to CUSTOM whilst the tone is actually playing. I think many users will have just replaced the batteries and it will go to acoustic mode by itself anyway without them realising what is actually happening here. Alex
Alex, thanks for the explanation on the differences between the apps and the three ways to enter acoustic mode. (That RFCx deployment ID feature is great, too!)
Yes, it does look like the time error corresponds to the time the app was opened, so that may solve that mystery.
Could the time error you see correspond to the time when the app was opened or started, rather than the time the button was pressed?
That's very strange. I'll let them know and put them in touch with you.
Yes, the 'acoustic mode' is indicated by a solid red and flashing green LED. The AudioMoth will only listen for the tone when in acoustic mode.
They will enter acoustic mode automatically on switching to CUSTOM if the time has not be set. You can also enable the 'Always require acoustic chime on switching to CUSTOM' option in the Config App which makes them enter acoustic mode every time, even if the time has already been set. The third way to switch to acoustic mode is to play a special tone whilst switching to CUSTOM. This is what the RFCx app is doing. It is also playing a different tone as it is also setting a 'deployment ID' in addition to the time. This deployment ID gets written into the file headers so that uploaded files can be linked back to the time and location of deployment. I'll follow up with RFCx also about the time setting as that seems strange.
Hi Alex,
Sorry for the slow reply--was out deploying AudioMoths last week!
I just downloaded and tried the Android AudioMoth app several times. The time set on the AudioMoth when I plugged it into the computer was correct every time. So, it seems this error is isolated to the RFCx Companion app. I reinstalled the Companion app today, tried it on a different AudioMoth, and encountered the same problem. (The devices are keeping time normally when plugged in to the computer.)
Another question--I noticed that the Companion app seems to switch the AudioMoth into a "listening mode" (indicated by solid red LED + flashing green LED) when the AudioMoth is switched from USB/OFF mode into CUSTOM mode while a long tone is playing.