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.
Official
Comments
If we both leave the house, in most cases only one of us is detected as leaving and the same for coming home.
Its detecting us as away when we are in the garden, just walking to the car (which is parked within WiFi range 15m from the house), sometimes its just triggering while sitting on the couch....and for this last case I haven't found any clue of how and why its triggering.
@Phuturist This would probably explain your issue, as you don't have high accuracy mode enabled. Ofcourse I can't speak for your phone, but generally GPS signals are only used when an app asks for it, and shouldn't consume too much power. Can you try turning it on for a few days and give any feedback on whether that solved your issue or not?
The reason it triggers when switching access points is probably because it has no internet connection for a very short time. I'll see if I can build a time-out or something around that. Another possibility is that the second access point is on another subnet, and Homey cannot be reached through it's local IP address, and high accuracy location mode is disabled on your phone.
A very real possibility is that your phone is a bit aggressive when going into standby, and is killing the wifi connection. Normally it shouldn't relay those events to the app, but that behaviour isn't really specified in Android. When your phone is in high accuracy location mode, you shouldn't have any trouble with this, as the GPS should kick in to verify whether you're at home or not. Can you check if your phone(s) are in high accuracy mode, and can you check if Homeys' location is set properly (you can check in the Settings screen)
It's GPS only, as cell towers aren't reliable enough. The range should be 80m plus the accuracy of the GPS signal and the (inverse) certainty of Homeys' location, so in most cases well over 100m.
Here's a screenshot of Location and I suppose its "configured" right?
Also received a flow-email when I left my work building.
Location within Homey is set correct and double check it this morning.
Is it possible to add a location check even if the app can find homey on the local ip adress? This way the vpn issue can be solved. You mentioned that on every network change, the check are performed. So the check could be like this:
- Network change detected (guess by the android framework)
- Check homey local IP
- check location
- if (location != home) && vpnDetected then !home
Guess there is an api call to check for vpn http://stackoverflow.com/questions/16355008/detect-behind-vpn-in-android
The requirements of home detection are pretty well defined: walking in should be detected as soon as possible, but going away is not really a problem; nobody gets hurt if your lights are on for three more minutes. Using these requirements, getting a GPS location isn't really an option, as it just takes too much time for your phone to get a GPS fix.
What we probably could do (but I'd have to test that extensively) is do a cell-tower based confirmation when you're on VPN. That wouldn't garantuee anything (accuracy to a few hunderds of meters, or even a few km) but the app would be able to verify if you're on the other side of the country, or when you're close-ish to home. But again, we'd have to test that extensively to make sure it doesn't take too much time to do that check.
If you like, I could test my use case .
I also experienced random false positives in the case WiFi was dropped. I solved this with a simple 10 pings threshold and works great.
If ping == OK then home
If ping == NOT OK and pingNotOkCount > 9 then phone/person left home
So maybe its an idea to make some sort of delay or threshold on the WiFi drop and so not directly act on one WiFi drop situation.
By the way, just in general: crash reports are awesome! Love those! If you encounter a crash, please report it. I don't really care that much about descriptions or other info, but the debugging information in those reports are so incredibly useful, they're almost as good as plugging a phone directly to my laptop
1. I left home almost 5 hours ago
2. "normally" this happens when I leave my work building
3. this time I did not left the building
Very strange and I have no idea why it triggered.....
When are devices that do not have the android app installed get removed from the list in Homey? At the moment o have 4 devices listed, but only one has the app installed (actually 2 entries are from the same device).
Perhaps as a reminder that when you factory reset / wipe an Android device, it gets a new hostname.
Because the app breaks compatibility with the old internal settings format you'll probably all have to log in again. This is expected behaviour and can't be avoided without very nasty tricks on our side. On the bright side: this allows you to view our now properly animated login screen
Work on the home detection is still ongoing. If it doesn't work properly, please report what happened, what behaviour you expected, and what the app actually did.
This is actually something we still have to build, but in our opinions it isn't that urgent because except for the extra entries in the list, there is no damage whatsoever.
When can we expact this update for iOS?
Also doesn't seem to crash anymore when switching between apps.