Thanks for the reply. pretty new to homey do you have a example of how to do this? would this be done in advanced flows? also on another note i have setup a danger zone in tractive under virtual fence to be notified when in that area. I setup tto be notified using the card in honey but it seems the card works for both a safe zone and a danger zone so i cant define just the danger zone. is there a danger zone card only?
Yes, there is.
Is there a way of creating to seperate fence zones so i can get notified on either safe or no go?
Hi everybody,
I’m looking for a way to know when our cat enters the home, to do some triggers.
eg. WHEN the cat enters home
AND the time is past 23:00
THEN close roller shutter
Would it be possible to do this with tractive?
I need this to be precise, because I’m trying to lock the cat in after a certain hour. If this goes wrong, I’ll be locking her out which would not be ideal.
I cannot use a smart pet door because it is in a flyscreen.
Thx!
Hello,
Just got my first TRACTIVE device yesterday, and I’m trying to use it to track my dogs precense, but the flow trigger cards are not working.
I tested two different triggers in different flows to see if any of them worked, but they never triggered. However, the tractive app sent me a notification of my dog leaving the virtual fence at 08:40.
Diagnostic ID: df7b58d5-fe18-4396-8886-2e9623e6db5d
Worth noting is that the flow card for when the tracker enters the virtual fence again seems to work.
Best regards
Hass
I’m the same. It was working great, but when we got back from holiday I noticed the dogs location wasn’t updating on Homey flows. I’m not sure when it broke exactly, anytime in the last month.
If I go to devices in Homey & click on the tracker, it says it is in a virtual fence, but it no longer seems to know which virtual fence in homey flows. I used an “And” Homey card for “in virtual fence Home” and the result out the card was “no” when tested. Tractive app reports both trackers are home, neither works with homey now.
This is the same issue I’m having. There’s a huge delay between when the Tractive app reports an event (like leaving virtual fence) and when the Homey app gets the data. Sometimes it’s a delay of around 25 minutes, sometimes the app has to be restarted to update the values.
I’ve done some testing, and restarting the app updates the values and the data pulling works for a few minutes.
I made a (really ugly) workaround that restarts the Tractive app whenever my frontdoor opens, and an advanced flow with multiple triggers that will act on whichever trigger fires first and set my dogs precense through a virtual device.
When I tested it this morning, the Tractive notification and the Homey notification fired at the same time when my dog left the virtual fence.
But yeah, something is broken in the way that the Homey app pulls data from Tractive.
I think the problem lies with Tractive, as Tractive is sending these events to Homey, not the other way around.
EDIT: You could send a diagnostic report right after your dog leaves the virtual fence and the Tractive notification is received so I can see if anything is received by Homey. Please provide a clear description and time in the diagnostic report.
Someone provided a diagnostic report, and I see what the problem is.
It will be fixed in the next version of the app.
Sorry for the slow reply…
I’ve currently got mine set up to change a yes/no variable for “dogs home”.
At the minute it sets the variable to “no” if “a virtual fence is left” so this acts as a cover all.
To get it to trigger when they are home, it looks for power saving which we only have set at our home virtual fence.
I’ll maybe set some notifications for messages for different virtual fences being left/entered & report back.
I thought the power saving zones were removed because I didn’t see any with the login I had, but I guess that person didn’t have any created (yet).
Can I use someone’ login who has power saving zones enabled, so I can re-add it and do some tests? Please send me a PM if you are willing to help.
Hi evdpol,
I have the same issue as the others. I’ve just submitted a diagnostic report: 52c1af41-7eaa-446c-bb6e-b1010349932e
My setup: I have a flow that checks the tracker every 5 minutes. My dog is at home, the tracker is connected to the known home Wi-Fi network, and the home location is configured as a Power Saving Zone in the Tractive app.
When the tracker is at home, the API sometimes returns:
{
“tracker_state”: “power_saving”,
“in_geofence”: true,
“geofence”: null,
“location_source”: “known_wifi”,
“latitude”: 51.5739,
“longitude”: 4.630129
}
So, `in_geofence` is `true` and the coordinates match the home location, but `geofence` is `null`. That means the app can’t determine which geofence the dog is in, so it can’t reliably determine whether the dog is home.
It seems to happen specifically when the tracker is in the Home Power Saving Zone and the tracker state is `power_saving`.
I’m happy to provide more logs, timestamps, or API responses if that would help. I’m not comfortable sharing access to my account, but I’d be happy to perform additional tests if needed.
Hi Edwin,
First of all, a big thank you for your app.
Unfortunately, I’ve been having trouble adding a tracker for the past two weeks.
Error message:
App version: 1.5.0
Could this be related to Tractive releasing a new generation of trackers?
Thanks for looking into this; feel free to get in touch directly if you have any questions.
Greetings & Thanks
Martin
I have released a test version which hopefully will restore the geofence and power saving zone functionality.
This version can be tested by installing the app here.
Let me know if it all works as expected.
I have done this in a evening and will be on vacation tomorrow, but I have some time to fix things if something is broken.
A new version of the app is submitted to the app store which restores the “Power Saving Zone” functionality.
Can you send a diagnostic report right after you see that error message, or did the new version solved the issue?
Hi Edwin
I tryed again. The new version solved the problem.
Great job, thank you.
Martin
This will be fixed in the next version. If I have a new test version available, I’ll let it know here.
