You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using OwnTracks iOS with the openHAB GPSTracker binding. I have using it for about a month and have loved it. It just worked all the time.
Until last night, when we went out, several km from our home, and the region triggers didn’t do anything. There is nothing in the openHAB logs and I didn’t receive the notifications I usually receive on my iPhone or watch. I doubled checked that the app was in Move mode, and that the setting for location sharing is Always.
This morning everything works as expected. One thing I thought to check was if the myopenhab cloud server were offline. According to the status page, it was online all day yesterday.
I’m unsure what else to try to troubleshoot this.
The text was updated successfully, but these errors were encountered:
I’m still experiencing seemingly random occurrences of a region trigger not firing. I have a series of regions around my home that trigger different actions: 1km, 500m, 250m and 75 m. Last night when we came home the 1k, 500 & 75 triggered as expected, but the 250 did not, though it did trigger a couple of hours later. (This is all as seen on openHAB through the openHAB.org mycloud server.
I am using OwnTracks iOS with the openHAB GPSTracker binding. I have using it for about a month and have loved it. It just worked all the time.
Until last night, when we went out, several km from our home, and the region triggers didn’t do anything. There is nothing in the openHAB logs and I didn’t receive the notifications I usually receive on my iPhone or watch. I doubled checked that the app was in Move mode, and that the setting for location sharing is Always.
This morning everything works as expected. One thing I thought to check was if the myopenhab cloud server were offline. According to the status page, it was online all day yesterday.
I’m unsure what else to try to troubleshoot this.
The text was updated successfully, but these errors were encountered: