rxritalin
commented
6 years ago I second this idea. Having native access to the HASS server via this app in a Tasker Plugin just makes sense as it would prevent the need to run multiple apps. The Tasker dev, Pent, is very active in his community and always willing to help. http://tasker.dinglisch.net/plugins-intro.html
While I would also argue that having native android device tracking as part of the app itself, it would be nice allow tasker integration for those that do not trust Google.
Creating alternate UI's and Widgets is where I would find tasker integration useful. Tasker allows for the creation of variables based on object states in the plugin, which can then be shared with other apps for the creation of UI elements.
rpeders
payano
Not sure how difficult this is, but adding Tasker support (via a Tasker plugin) would be not only be a great improvement to this Android app, but also to Home Assistant at large. Because Tasker is integrated so well into your phone, this would enable much simpler and more natural automations.
Just as an example: a Tasker plugin that enables setting entity states would allow for easy presence detection in Home Assistant without the need for setting up an MQTT server (or even to turn on your phone's location services!). You could just use Tasker's "Wi-Fi near" state to trigger updates in Home Assistant (either flip switches or directly update a template). This way you wouldn't need to run GPS and Owntracks, eating up your battery and sending out your personal data.