Hi there, I used local time to configure our audiomoths a couple years ago. We were near Tahiti (so UTC -10); however, I used my computer on Pacific time (UTC -8) to set some of the moths. I assumed that since my computer was 2 hours off, I would need to correct the times later. But, the strange thing is that all of the time stamps are correct for local time. For example, I deployed two moths and they both were supposed to start recording at 8am but they were set with different computers on different UTCs. So, one file will say 08:00 UTC -10 and the other will say 08:00 UTC -8. I expected the one on UTC -8 to say 10:00 (which I could then correct to the right local time). I am concerned because I thought the embedded file information was accurate, and was using that to correct other files but that does not seem to be the case here. Hopefully I am just missing something obvious here! Any insight would be appreciated - thank you.
top of page
To see this working, head to your live site.
5 Comments
bottom of page
Hi, I can't quite follow the sequence of configuring and deploying that you describe. When you say 'configure' do you mean setting the configuration with the Config App? When you say 'set some of the moths' do you mean setting the time with the Time App or the smartphone app? Internally, the AudioMoth always works on UTC. This means that schedules and the internal time is always stored as UTC. When you select local time in the config app, you are just setting the local time adjustment used when displaying the schedule in the configuration app schedule at the time of configuring, and the timezone when generating the filename and the WAV header comments timestamp on the AudioMoth. This means that if you configure and move to another timezone, the AudioMoth will still make recordings according to the original UTC times that were requested when it was configured. The recording time in the WAV header comments, and the filename, will always be the correct time that the recording took place (reported either in UTC or in the timezone that it is was configured in if local time was selected in the Config App when it was configured). If you check the CONFIG.TXT file it will report the UTC times that the scheduled recordings will take place, and the timezone that is used when generating the filename and the WAV header comments timestamp. I'm not sure if that explains what you are seeing here? Alex