Oh man.. sorry words are hard sometimes! I see where I messed you up. Can you go back up and re-check that post, I cleaned it up would should make sense now.
Long story short, If you have that "Use GPS for higher accuracy..." slider checked like your picture, the other settings you asked about will always be using higher battery from the GPS. The settings were meant to have the HE app toggle the phone from high power to lower power as required.
Ok, this should fixed in the next version. The forked APK sends back "dirty location packets" (accuracy error too high, phone failed to get a location, etc) as a keep alive. They were to only to be used to update the 'last update time' and to pull back settings in case something got messed up but I had it routed into the tile as well.
Latest version of HD+ supports it. I deleted my 2 Life 360+ tiles and replaced them with the corresponding Owntracks ones. With the latest HD+ just ensure that the Owntracks devices are enabled in maker api and that's all that's needed.
Is Region an attribute, that we could use as a trigger for Rules or etc. If not can it be added?
I would think so, as I think any attribute can be. Are you running into an issue that is making it to where you can't use it?
I don't see it as a selectable attribute for tiles or rules, unless I am missing something.
I must say, I think that “null null” is a great nickname for her…
To see what's available from a device, you can check In Rule Machine - you can see the available attributes for a device by selecting Custom Attribute as the trigger type and then choosing your device...
Correct, that's why I said I don't see Region.
I'm using an Iphone, IOS app, its missing StreetAddress for now too, and a few other attributes too, are you using an Android phone?
Can't you just use location? Location=Region when a region is entered.
Trigger: Location changed
If location = [region name]
Then...
Won't that work?
ahhh, location is region in attributes, missed that, thank you!
If you don't have a region specified for that location, the location attribute gives you lon and lat, that's why I missed it.....for an Iphone that is.
I'm running Fully Kiosk too, on Fire Tablets, but mine is the paid version (Plus) with popup on and Larger or smaller Maps don't work either.
Something wonky with lastspeed. I had the cruise set for about 10 miles at 60 and the mph on the tile never got above 38 it was changing, just not reporting close to accurate speed.
Wonder if that will hold up in court. No your honor my hubitat dashboard said I was going 38.
2.4.17
Our home address.
They are quite consistent, you can see these 3 just popped up 1 second apart.
dev:21382024-01-27 15:13:22.496errorjava.lang.NullPointerException: Cannot invoke method split() on null object on line 480 (method generatePresenceEvent)
dev:21382024-01-27 15:13:21.809errorjava.lang.NullPointerException: Cannot invoke method split() on null object on line 480 (method generatePresenceEvent)
dev:21382024-01-27 15:13:20.799errorjava.lang.NullPointerException: Cannot invoke method split() on null object on line 480 (method generatePresenceEvent
Don't know if this is related to my issue above but I'm stuck in Norway now and, even though my attributes are updating, I now have a battery optimized/restriced message and my app is not.
EDIT: flicking al the movement and waypoint widgets I managed to get home but the battery optimization attribute refuses to budge so far.
The iPhone and Android Play Store versions don't report an address, that's why there is no street address. I'm just wrapping up allowing you to link the HE app to a geocode service to backfill those missing addresses.
Interesting. That would come directly from the phone app. I have seen that it doesn't always report a speed though.
The null/null/Norway will be fixed in the next version. It's the poor accuracy locations that seems to be messing with the tile.
As for the battery optimizations, when you look at the OT app on your phone, and look at "App battery usage", it's set to "Unrestricted". If it is, and you are on that screen, click the "force stop" and then "open" buttons to reset the app.
Yes I have tried that. Cleared the cache too.
App starts again, refreshed my HE device and stays * batteryOptimizations : Optimized/Restricted
I have never had this in all the time testing both of our phones.
I'll try reloading the app.
Deleted app and reloaded with Location and battery set to correct options:
dev:21372024-01-27 18:39:53.733debugApp settting: 'App battery usage' is 'Optimized' or 'Restricted'. Please change to 'Unrestricted'
Hmmm
EDIT:
Deleted the APK and HE device.
Reinstalled and my wife and I both have the "split" and battery error permanently now. Never had any of this before. hers is a a bit different than my attery complaint.
dev:21382024-01-27 22:24:02.558errorjava.lang.NullPointerException: Cannot invoke method split() on null object on line 480 (method generatePresenceEvent)
Me, Pixel 7 Android 14 * batteryOptimizations : Optimized/Restricted
Wife, Pixel 5 Android 13 * hiberateAllowed : App can pause
Download the Hubitat app
