Can’t really find you an answer. I would recommend asking locative.
Their twitter seems fairly active and they have a place for support requests.
I also seem to have the same issue. Recently set up SSL and it seems like HA does not get the location updates from Locative.
I was able to get home assistant to update my location by entering this into a web browser.
https://my.duckdns.org/api/locative?api_password=<pass>&latitude=<lat>&longitude=<long>&device=scottphone&id=work&trigger=enter
The problem is, I don’t think locative has a field for your device name, so maybe HA is just throwing an error due to locative not knowing an appropriate device name?
I figured my problem out. Locative creates a new device in your known_devices.yaml file. Make sure you are using that random key that locative selects as your device.
I would suggest you augment the documentation for Locative with your discovery =)
sgauche,
When you say the same issue, was the test-connect in the Locative app also hanging for you as well?
No response yet from Locative on my support request.
The test button in locative has hung for me when locative was not working and also when I got it working.
1 Like
Is it still working for you?
Do you use the latest version of HA and the app?
Do you use “post” or “get”?
I am not able to make it work here.
I switched back to OwnTracks, sorry
do i include the port number (8123) in the <ha_server>?
I’m having trouble with Locative reaching HA (0.33.4) as well. My . yaml checks out fine, but when I send a Test GET from the Locative app it just shows a “Loading” loop. I’ve tested that 8123 is open to outside and I can access HA. My router uses Gargoyle (OpenWRT). When I enter into my browser:
"Forbidden
Rejected request from RFC1918 IP to public server address"
“This site can’t be reached”
Any clues would be appreciated. I don’t know if it’s related to OpenWRT or not in terms of accessing the HA server
Correct me if I’m wrong, but it makes no sense to use a link like:
http://<ha_server>/api/locative?api_password=<password>
with the password in the url.
Locative works in background and can send updates while connected to public wifi. With or without ssl, the requested url can be captured (very easy) and then anyone who does it will be able to access your server.
From there, they can get your home address (gps coordinates) and full control of everything you have connected (worst case - door locks).
- for Locative to work HA needs to be accessible from the internet.
I think its not as bad as it seems (at least if you use https!)
Just noticed that locative is being shut down. Not sure what this means for HA support. The apps are open source.
I didn’t realize that it was shutting down! Here’s a post about it from the Locative site…
https://blog.locative.io/bye-everyone-df01871fe949
Although, it looks like the app will continue to work as-is without cloud service. I don’t think that I’m using the cloud service right now as I don’t have an account for the Locative site. So I guess integration will be fine for a while if you don’t use the cloud service.
1 Like
This is true. I was thinking of implementing a windows 10 version and using the Locative API to communicate with HA. Maybe when I get some time I will set this up 
1 Like
A old post. but 1 week ago there where some improvements on the iOS app.
Now its version 4.2.8