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
No problem, i can make a cli install also tonight at home.
Tnx
Can you check if you have sharing enabled in your fence definitions?
If that is not enabled, the name of the fence will not be included. In the message.
From your log:
'{"_type":"transition","tid":"or","acc":82.5,"event":"enter","lat":47.xxx,"lon":8.xxx,"tst":xxx,"wtst":1491827105,"t":"c"}'
I am missing the "desc" field. That includes the name of the fence and is needed to match the trigger card.
This packet is sent with Owntracks to the broker:
{"_type":"transition","tid":"pb","acc":50.22695,"desc":"home","event":"leave","lat":XXX,"lon":YYY,"tst":1491844872,"wtst":1491596181,"t":"c"}
I have double-double checked the channelname (/owntracks/<user>/<name>/event
Nothing happens...
What am I missing here?
EDIT:
Found it! I had set accuracy in settings in the Homey to 50... that's too low. Setting it back to 250 solved it.
The / before owntracks should be removed. Or use a topic like owntracks/+/+/event
Then it will trigger for all users and devices.
- owntracks/# topic is added by default.
- Voice capability added (NL / EN). You can ask "Wat is de locatie van xxx" or "Waar is xxx" and homey will tell you the geoFence that person is in.
https://community.home-assistant.io/t/android-owntracks-and-ibeacons-ibeacons-not-seen-by-owntracks/9756/4
Also my iBeacon (ByteReal) has 3 transmit power settings. Unfortunately even if I set the tx to the low setting it is still too high for close proximity detection (I want to open the front door when I'm max 3 meters away). It sees the beacon in the whole 90m2 apartment.
That's why I just switched to an android phone so I can test if NFC will do what I want (iPhone doesn't have NFC available).
Is Owntracks also useable in a 'current location' flow? I mean...just like the Presence detection had the ability to use cards like "if some is at home..."
Since Owntracks works so much better than any presence detection I've tried, I'd like to use this in situations where flows will only run when I'm nog at home.
Do not update to the latest mosquitto broker if you depend on the correct working of the owntracks app. Mosquitto has patched a security issue and as a result the mosquitto broker thinks the owntracks app on your phone is a malicious client.
The owntracks app on your phone uses your username and devicename as client ID to connect to the broker as username/devicename. The security patch detects client id's with a #, + or / in it as malicious.
The people at owntracks are aware of the problem and they will publish an update in a few days.
The homey app does not have this problem as the client ID has a different format.
As a workaround you can edit the clientId manually in the new option configuration management in the latest version of the owntracks app on your phone.
At the moment the owntracks app does not have a condition card. But I am looking at that.
But you always use a counter and check if that counter is 0 or not.
You mean something like this:
Greetz, Danny
I have set Homey on a range of 50mtr and my Owntrack app in my Iphone on 40mtr. When I leave my house, I have to 'loop back' following the road. So after a few minutes I sort-of drive by my house again.
At that moment, my Homey sees me 'returning home'....and 50mtrs further down the road, Homey sees me leaving again.
So..I was thinking it might be because of the distance, but...checking this I noticed that in a straight line, I'm driving by my house at 128mtrs.
So...this should be well outside the set ranges in both my Homey (50mtr) and my Owntrack app (40mtrs).
How to solve this? Is this where the new option 'check for double events' is for?
The problem you have has to do with the accuracy of your GPS. The "check for double events" will not solve that problem. That option solves the problem that when the gps accuracy is too low and gets out of range (the value specified in the homey app), the leave event (or enter event) is not triggered. When the gps accuracy is again within range it can generate an enter/leave event again. This scenario is solved with that.
In your case the best thing is to play a but with the geofence range and the accuracy.
But need to think of a suction for that problem. But that's not easy. If you use a timer for ignoring events will also cause problems.
But I am open for good suggestions.
Go to settings and add the users and geofences.
(or use the cards where you can enter a topic).
The homey app will add geofences and users when it receives them from the owntracks phone Apps. Also the data is persistent (all gathered data will be stored when the app closes when updating or restarting homey)
If you go to settings of the homey app, are there coordinates and battery level behind your username?
Or check the log to see if you receive messages from the phone app.
Remember that geofence enter/leave messages are sent when actually entering / leaving the geofence.
Also please tell me what you have done already. Did you create a trigger and if so what card did you use?
Added 2 users as said but nothing happens. I use the same name as the deviceid
and this is my flow.
i added the extra lines in the mosquitto.conf
I receive a messages from owntracks that i left the area but i dont receive a push message from homey. I would like to use it with 2 users.
The userid is admin.
So if you change Dave into admin in the trigger card, you will get the notification.
You should create seperate users on your MQTT server. So create a user Dave and Ingrid on your MQTT server and it should work. Right now you have configured a user admin with two devices named Dave and Ingrid.
If that is not an option, use the trigger cards where you can enter the topic. Use topic owntracks/admin/Dave/+
But with this option, asking homey for the location of a user will not work correctly.
The best (and correct) solution would be to add different MQTT users.
Are you still using owntracks? Would you consider updating the guide with the latest changes?
Did you create the users on the MQTT broker and are you logging in with the phone apps with those accounts?
According to the Screenshot, you are logging in on the MQTT broker as admin.
That is why the homey app is adding the admin user.
If you remove all the user data from the homey app and let the owntracks phone app send a location message, does a user get created in the homey app?
Most important is the user part and authorisations and the MQTT server.
Besides that, a condition card has been added, speech has been added and a phone battery trigger card has been added.