This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
Then messages are not received by the homey app. Please check the log. Try to generate some messages on the owntracks app on your phone and the check the log on the homey app and see if messages are received.
My Regions keep showing as a waypoint:
Tried, changing the radius to 0, then wait a while and change the radius to 250:
Still returning a Waypoint not a fence..... What am I doing wrong....
edit: i also see this
20170701-08:41:06 rejectUnauthorized: true
20170701-08:41:06 Subscribed to owntracks/#
20170701-08:41:06 MQTT client connected
20170701-08:41:06 Connected Topics: owntracks/#
Can you also check if the log is correct?
edit: today i noticed that the significant changes mode does not send the location to the broker
Indeed, manually pushing location updates does work and the log shows that it receives a location message.
When I leave a region I do get a notification on my Iphone but no location is being shared to Homey... Is this a bug in the Owntracks iPhone app??
Does changing to move mode work for you @Deef_K ?
Did you check if you have 'share' enabled in your regions?
If you did not, the geofence is not reported and as such never trigger on enter/leave events.
@LJSVV the same for you?
So I think it is owntracks iOS related. Already issued on GitHub...
EDIT: after deleting all fences and after re-adding it seems to work right now..
@LJSVV also tried that but no luck.
No transition messages (events) received by the server...
For the moment I will fallback to the IFTT multiuser solutions for presence detection....
i.e. battery (from Android) is reported, however not from iOS.
Leaving/arriving in home fence not working on android and not on iOS.
Leaving/entering work fence works 1 in 5 times for iOS, never on Android.
I might try to reinstall everything next week and give it another go.
@LJSVV which IFTTT multi user solution are you referring to?
How did you set everything up? It's working great here. I don't have an iOS phone, so can't test anything on that, but enter / leave events are working great. Could be GPS related. Please provide me with settings of the android app and the homey app. Also how did you setup the MQTT server and triggers.
Also there are sadly differences between the iOS and Android versions of the owntracks app. Some things work on iOS and some only on Android.
I am using IFTTT for presence detection. My wife's iPhone has an own IFTTT account. When adding the Homey Channel to the IFTTT account on the second phone, Just login using the account used in the Homey IFTTT app. This works perfect. I am using the different away or at home flows mentioned in the first post of this topic, but than with an IFTTT event trigger.
Thanks for the quick reply. Unfortunately, I already deleted the settings on homey and the apps.
I was using cloudmqtt (might cause some of the problems; however, I did see data in the logs of Homey).
Regions are shared and connections could be made.
Perhaps it had something to do with my flows (those I still have, I added 3 as an example):
@LJSVV thanks, I'll use that as a backup in the meantime (did not know you could couple the same Athom account to multiple IFTTT's).
I'm using the iOS app so maybe that could be the problem?
I don't have a iPhone, so I can't look into that. On my android phones the transition events are working.
I read that there were problems on iPhone with enter/leave events, but can't find if they are resolved or not.
This weekend I am going to upload a new version that has http support. Perhaps there is a problem in the combo iphone/MQTT.
You are sure the settings are correct? You made the geofence public and set a radius?
These are the Owntrack Client settings in Homey:
If there's anything that I can do to help to investigate this issue, please let me know. You can always send me a DM on the Athom Slack chat. My username is @rido.
Thanks ;-)
Up to now using topics was the main way of identifying users. This is no longer the case. The owntracks app listens to all topcis that begin with owntracks. For MQTT users, the username is retreived automatically from the topic the phone app posts on. So it is important that you use correct usernames.
Also with version 1.5.0 it is also possible to use HTTP. HTTP can be used on its own (without a MQTT broker). The use of a MQTT broker is still possible and has some advantages over the use of HTTP.
When using HTTP, you have to add users that are allowed to send events to the owntracks app. To do this, go to the owntracks settings page and go to the second button (Change users). Add the user name that you want to give access by entering the name in the empty field below the already known users. Press the "+" button to add the user.
After you have added the user, the user will show up in the user list and it will have a token generated that is used in the phone app to allow receiving of the events:
You can remove a user by pressing the "-" button. The "#" button can be used to generate a new token when you think the id has been comprimised.
In the app on your phone, you should select HTTP as connection:
Then select HOST:
The URL you have to enter here is as follows:
https://<cloudid>.homey.athom.com/api/app/nl.scanno.owntracks/events/?token=<tokenid from user>
where <cloudid> is the Athom Cloud ID of your homey that you can find in Settings/System.The tokenid is the id that is generated when you added the user.
Using the Athom Cloud is the easiest way of getting started with owntracks. If you are more skilled you can also directly connect to your Homey by port forwarding. Keep in mind that homey itself does not support TLS/SSL. If you want to have a secured session, you need to use a proxy.
When the owntracks app receives an event with a geofence is does not know, its automatically added. The main purpose of this is that in the trigger cards you do not need to enter the topic names anymore (When using HTTP you cant even use them because HTTP does not use topics). The new trigger cards (they are already present in the current version of the owntracks client) allow you to just enter user and geofence:
However I see you are adding very nice stuff so I will look into it in the near future, keep up the good work!
With the new version 1.5.2 you have to enable MQTT. I have added a new setting (first checkbox) that is disabled by default. Now that HTTP is introduced, the need to use MQTT is not mandatory and for most users it is easier to just put in an URL then to create a MQTT broker.
Using MQTT has advantages above using HTTP.
I presume that is a typo "you do NOT need to enable MQTT"?
Nope. What MQTT is disabled due to a new setting. Current MQTT users need to check that checkbox to be able to use MQTT.