App verwijderd en opnieuw geïnstalleerd op homey en nu werkt alles weer
Got my tracker working fine and sending notifications when it is switched on or leaves the safe zone. But it is not reporting when it has been switched off !
Any ideas ?
Andrew
This app now appears to have stopped working for me.
Can’t log in to “tractive servers” even though i can log in direct on to the tractive website or phone app using the same credentials.
Is this still working for others ?
Hi
I have the same problem.
Got the gps 3 weeks ago and everything worked great, but now im not able to login to tractive in homey.
I managed to make it work again by restarting the app, but now this happened multiple times. Can you have a look at why the app needs to restart?
And I have a request.
Is it possible to add [Status :Charging] to the When cards?
Thank you!
/Magnus
Yup, a restart was the only way i got mine to start working again, but it has been ok for the last week !
Andrew
HI Magnus,
I will add this in the next version.
I have to restart the app ~daily to get it working again (red triangle icon) - after that all is well (until it isn’t). Any tips for troubleshooting?
What is the error message?
Send a diagnostic report when it happens, please.
Apparaat onbeschikbaar
Start de Tractive app opnieuw op.
(Device unavailable - restart Tractive app)
Will do! Thanks for your support
Edit: tried to send the report but got an error there too: bad gateway. Not sure if you’ve recieved it? b1ea2555-476f-4372-8032-c70f256625dc
Ah, I can see the problem! Thanks! Will fix this in the next version.
Great, thanks so much!
The cards are available in version 1.4.0, which is now live.
This should be fixed in version 1.4.0, which is now live.
Please send me another diagnostic report when the problem persists.
Thanks for the fast turnaround! I will keep an eye on things - no news is good news.
Thanks again!
Unfortunately it happened again Just sent you the report
ebcd42b6-3f0d-483f-b2b3-df529558a71f
That is weird, there isn’t any error in the report…
Tried to report again: e277b68b-3cfa-4421-aae1-155d524d2505
I published a new version of the app which should fix it
Please let me know if this solves the problem.
1.4.0 → 1.4.1 and keeping an eye on things again.
Thanks so much for the continued support, we’ll get there