I am tech helping to service a pretty big (50 trap) AT220 grid. When we have to service these traps, we typically have a team of 3 techs, each person servicing a third of the traps within the overall grid. When servicing traps, each person is logged into the Trap.NZ app on the same account, we have a general account for the entire organization (we also have our own personal accounts but use the organizational account for trap servicing), The idea behind this is to have all the trap data syncing to one location, so anyone can find and then view the data for all the traps in one report. Would this be the best way to setup a trap data syncing project for an relatively small organization?
The main reason I am asking this question is that I have had trap data go missing, by which I mean, when each tech has finished servicing their set of traps and then synced their data via the phone app, the information for some traps does not appear in the trap report online. So, when I come to analyze the latest trap data on the website as much as a third of the traps are not present in the report. Is this an issue with the individual traps, the phone app or the way our organization has the syncing set up - multiple users syncing to the same account or maybe user error on my part when accessing the reports?
We have not yet serviced the traps in question again, but will do soon as part of the bait/battery changing cycle. This means I do not know if it is a individual trap issue - the exact same traps not uploading their data - or whether this issue is just a freak occurrence.
Sorry for the long post, but any advice or help you can give will be gratefully received
I service a pretty decent sized grid as well and lately have had my fair share of issues with the new app, the old app was awesome. I wouldn’t be surprised if it’s a combo of all 3 if I am to be honest.
If you are logged into the project as that primary user, and that primary user collects the data then only that primary user can see those traps, no other members of the group can site each others records, that what we have found.
We have had to set up different API credentials per user that then syncs to our database, so we can see all traps relating to our project.
At least the data isn’t missing and should still be on the trap for next time your visit though. It’s a shame that we dont see offline records on our devices, this is something we should be campaigning for, so at least if the sync fails, we can manually add records.
I have been taking screenshots of each trap, which isn’t great, but at least you have a backup, though I have to admit, i did’t do that last time and only a 1/3 of my traps made it to the cloud.
I wish I could help more, but we are guinea pigs until they get all the bugs out of their system.
@alanghudson there’s a few items in this thread so 1. It is always best for each member to have their own unique login, this means the records will be in each users name and any issues identified quickly. They can then be added to the project and their records will still sync to the project. 2. If the records are not migrating to the website, have they checked the logs to see if they have any error messages? (yellow exclamation mark icon) If they do they need to export the logs as a debug (JSON) and email to themselves and support@trap.nz where we can repair the logs and enter them into the project. If this is the case they will also need to undertake a hard reset of the phone app.3. They should check the cloud icon in the top right of the map screen to make sure the app is set to upload the records via either thee wifi or cellular service. If the issues persist, contact support@trap.nz so the developers can investigate this.
Judging by both your responses, I think we have set up the data side of the projects wrongly. We currently (to the best of my knowledge), don’t have any projects setup, we just sync the data with the same user login amongst the multiple techs servicing the traps and then read the NZ AutoTraps AT220 Telemetry Report for each trap, to access and then use the data.
Looking forward, we should probably setup each grid of traps as a different project (our organisation has several but most are only a handful of traps). It seems you can setup up individual trap lines within a larger grid, which sounds useful. We would setup the projects under the organisational login, but then each individual member has their own login and is added to each of the projects that they will be involved with. Does this sound correct? Is it easy to add existing traps to a new project?
How do you check the logs via the app? The number of missing records vary between techs but all the traps were serviced on the same day, just some of the trap data synced to the server and some didn’t. It appeared pretty random which traps did and did not.
Kia ora @alanghudson it probably would be a good idea for us to have an online meeting so we can go over all these things and demonstrate if needed for you. Otherwise, a organisation can be a good way to “umbrella” multiple project. Or if it is a new area in a project a project can have multiple map polygons. You can tag installations to allow for reporting on specific areas or lines within the project. And yes every member having their own login is a good idea. Logs can be found in the menu (the three horizontal lines in the top right of the phone app map) If you would like some help contact support@trap.nz and we can set up a mutually convenient time to have a meeting.
I will pass this on to my boss about having an online meeting. I have had a look at the NZ Autotraps app, clicking on the 3 lines brings up the headings: “Tech Details”, “Traps Visited”, App version and “Log Out”. None of which seem to lead to logs of individual trap data. Where can I find this?
@lenore-admin, I didn’t know there was a separate Trap.nz app, that looks useful for when we have made projects for our trap grids. However, certain trap records seem to be missing from the NZ AutoTraps AT220 Telemetry Report section of the Trap.NZ. Is this data recoverable and if so, what would be the best way to do this?
@warik so the old trap data (cycles, strikes etc., old battery level) would still be present in the traps and then would be re-synced when you connect with the app to the trap, or would the most recent trap data overwrite the old ones?
Its not a dumb question. But in my experience it is the most recent data. They just released a new version, but I doubt very much that it will keep those individual records per visit.
The old app included this feature, and it’s something I’d really like to see again. Currently, needing a trap.nz account to use the app feels like an extra step that could be simplified.