Yes, that is possible to do.
Thanks, great app!
I’m getting a lot of errors in mosquito: client arielamqttclient already connected, closing old connection. May be related to multiple devices indentifying with the same name. Would it be possible to add a random number (per device) to the client ID? Also seems common practice in other clients 
Thanks
Mats
Thank you for the suggestion. Let me see what i can do about this.
LE: next version will contain this fix.
Hello all,
Version 1.3.5.2 is out.
What’s new:
- NEW: WiFi & Zone assigment device tracker feature
- NEW: MQTT & mobile_app device screen status sensor
- removed home wifi setting (replaced by WiFi & Zone assigment)
- fixed entities device name invalid display
- use dynamic allocated client name for MQTT connection
1 Like
Since the update, I don’t see how to add my home WiFi?
When you use zones, home zone is in my configuration yaml file, not in my zone file. So I can’t use your new method to attach my home WiFi to a home zone.
I will add some modifications and any wifi that will have assigned a zone.home will be considered home wifi.
I’m not really understanding what you mean. You say that zone.home is not listed in Ariela?
Correct. No option in drop down for my home WiFi
Strange. Please share the logs so i can check it out
Sent logs. I believe due to documentation and how HA is handling notifications a lot of people are confused.
Not sure how your new code handles the switch off from the “zone via wifi” and back to GPS. Usually when I disconnect from Wifi, I am still in a zone (100M) and don’t want to see a notification just because I disconnected.
1 Like
So recently i switched over to using nabu casa. Remote access and everything works well, but there is now a delay in location reporting compared to when i was using a direct DNS connection. When opening the Ariela app it takes a while to connect and bring up the UI (up to 20 seconds sometimes).
The issue is i get an alert when a door is opened while I am away. But since moving to nabu casa i can be home and opening doors etc for up to a minute before it reports my location as “home”. Any tips to improve the responsiveness? I have just enabled “allow background running” should that fix my issue? The result is that i now have a permanent notification icon, even when i “swipe away” the app to close it.
My current device tracker options :
- Device trackers enabled
- Update mode Device tracker - Mobile App enabled
- Tracking mode is GPS
- Updates period is 1 minute
- Updates position is 50 meters
- Wifi zone is setup
Just enabled Background running for the app, but i know this will use more battery, and has the persistent notification. Will see if this improves things when i arrive home.
Any other tips?
Hello,
Do you notice delay when using web ui also?
Indeed the allow background running should do the trick. The notification can be disabled from Settings -> Apps -> Ariela , and if you do not have many sensors enabled you can have relatively few percent battery usage.
Once it’s connected it’s fine, just like navigating locally.
I have no sensors, so I’ll see how the battery is affected today. Thanks mate
1 Like
HI all,
can some one tell me which card are officially supported by ariela? I wuold like to create a useble ui for my mobile phone.
Thank you
Hello
Here you can find which lovelace cards are currently supported.
2 Likes
So I tried with enabling background running. It was better, but still not as good as before, still not quick enough to pick me up as home before i open the front door.
I have gone back to disabling the background running to preserve the battery life. What is the auto-reconnect feature about? is that just for when browsing the UI in app or is that for location reporting too? It is currently enabled anyway.
I have cleared my current config, and set everything back up again, will see if this has helped.
Edit for clarity: I also tried going back to duckDNS and that didnt see the improvement i wanted, so i figured there must be something else going on, hence clearing out all settings and starting again. At some point my zone.home wifi was cleared too, so that may have been a factor.
The auto-reconnect feature is for the moment when Ariela is running in background. This feature will make Ariela automatic reconnect your HA server if for example you are switching from 3G/4G → Wifi or viceversa. I suggest using this feature too to check it out if its improving.
For a few weeks now my familys device_trackers are not updating from Ariela, unless the app is open.
This have not been an issue before, and no settings have been changed since it worked.
I hear from friends that they have same issues.
How do we fix this?
From Ariela -> Settings -> Common -> Enable “allow background running” option. If still not working, you will have to delete integrations from HA (since a lot of changes been made on device tracker in the latest updates). Please let me know if works
Ok, I’ll re enable it and see how I go this afternoon. And make sure I’m not force closing the app too yeah? My wife is guilty of this one…
Ok. Also you can use mobile_app device tracker and even if Ariela its closed (forced closed) it will wake up from time to time to update that entity.