Nope. They need to be GETs !!
That is the first thing in @ogiewon post.
1 Like
@steve.maddigan , apologies again for delay while away on business. I changed the Locative settings (webhooks) to GET, and still getting Locative error notifications every time I enter or leave the geofence- but the errors are different now. So strange
Not sure that is an error any longer. Looks like it may be the reply response from the Maker API GET call.
In the Locative app on you phone, check the settings to see if you have Debug Notifications enabled. If so, turn it off and try again.
No, debug is off
Well, if you take one of the URLs from your Locative app, and then paste it in your browser address bar and click enter, do you get the same text returned?
I personally do not use Lovative’s built-in notifications. Instead, I have Hubitat send me a notification whenever anyone’s presence sensor changes state.
Actually, if I paste one of the URLs into browser, I get an error "missing authentication token"... BUT, you're right... this isn't worth spending more time on because the arrivals/departures are working - I should notify in a better way anyway, than Locative's notifications. I'll just turn them off and forget about this. THANK YOU and @steve.maddigan so incredibly much for your help!! On to my next project, linking ST to HE. I'm on that community page trying to find info about Hub Link, as it's supposed to be a Built-In app but I don't have it showing up.
1 Like
That is a real error, indicating that a portion of the URL is missing. My guess is that the copy only grabbed part of the URL before you pasted it into your browser.
1 Like
Cool.
Yeah, I just send a notification from HE (I use pushover) when the rule triggers.
Edit. Actually I send a notification from my lock controller RM when it acknowledges that I am truly home or away. That really all that matters to me.
Yep, the whole url hadn’t copied (MAN, you’re good!!). When I pasted whole thing, I got same error as Locative’s notifications
1 Like
SmartThings is eliminating their Groovy platform altogether very soon. I would not waste any more time trying to get the old Hub Link code working. It was developed back in early 2018 to help original ST users migrate. But it has received zero updates for a very long time. "Hub Connect" is/was a community solution, but again it depends on the old ST Groovy platform. Also, its original developer has left the Hubitat community.
Is this an error or just the typical acknowledgment string?
1 Like
Great! Just to be clear, this is not an 'error'. It is simply a proper response from the Hubitat Maker API app to let the calling system know what the current value is now.
1 Like
Unsure in browser but Locative app calls it an error
I get the same thing.
I think locative is calling it an error bc it doesn’t know how to parse it.
Side note: there is a thread on here somewhere discussing how to parse the response but I didn’t go that deep with it. I prefer the ack from RM when the action is carried out.
Ugh. I’ve got a few things that can’t be done in HE. My Somfy blinds & curtains can’t be done because the drivers were written for MyLink and/or TaHoma Switch. I have TaHoma HUB, which is the upgrade from MyLink. And TaHoma SWITCH driver requires API access, which Somfy doesn’t grant in the U.S.
Ah, I can’t help you with those - lol.
I’m still trying to get arp’ing to work on my edgerouter. I do not like Linux. And I can’t nfs map the drive so I am using the bloody vi editor. Ugh.
Looking for assistance I'm assuming with the configuration of the Locative app on my iPhone 14 running iOS16.2. The URLS in the webhooks work when typed from a browser. Wondering if the configuration is correct here:
The webhooks are set to GET as well. Like I said, the URLS work from a browser and the Locative app shows me going/coming out of the geofence correctly. But it also shows a no response error on the notification panel. Any ideas? Documention is hard to pin down on this.
Your Locative Settings page looks like mine. How about your actual Geofence Location in Locative?
Assuming you're using MakerAPI with two Cloud Endpoint URL's - one for arriving, and the other for departing, right?
Yes. And those endpoints work when sending from a browser.
Actually you can SELECT ALL in the webhook URLS and click "Open Link" and it works. I.e. shows arrival and departures. But when the app tries to send those it gets NO RESPONSE. Weird.
