DISCONTINUED HA Client - native Android client for Home Assistant

Now it connects, but I miss lots of entities (no lights)

Guys, I want to thank you all for your help. But it is very hard to fallow all issues in one forum thread. Please report your issue to HA Client public repo on GitHub and we will sort it out one by one. Thanks!

This is already a progress :slight_smile: Please report this issue to HA Client bug tracker.

It’s working now since the last update :slight_smile:
I did not have to change anything.

1 Like

I’m skipping entities that can’t be parsed. I think this is the reason.

Oh, that makes sense. Thanks!

1 Like

Ok, I created a new Issue on Github with some missing entities.

1 Like

Is this working with groups? Personally I moved away from groups and work only with Lovelace

Yes, for now it works only with groups. But Lovelace UI support is in plans.

Will you be posting the source code?

What’s the difference between this client and HomeAssist?
Does it support Lovelace UI? Is there a chance for IOS-like actionable notifications in the future?

Yes. Not now, but definitely will.

1 Like

I’m trying to build a client that looks and performs as an original Home Assistant UI. My main goals is speed, widgets, wear os support and native notifications.
Lovelace support is planned as well.

3 Likes

You should add themes too

1 Like

Good idea. Thanks!

1 Like

Version 0.1.2 is in Google Play. With groups parsing fix and extended errors logging.

1 Like

So here’s my log I think I’ve got everything set up correctly but front end showing blank.
HA VERSION: 0.78.3
Local HTTP: 8123
AUTH TOKEN

[Debug] :  AppLifecycleState.resumed
[Debug] :  Socket connecting...
[Debug] :  [Received] => Message type: auth_required
[Debug] :  [Sending] ==> auth request
[Debug] :  [Received] => Message type: auth_ok
[Debug] :  [Sending] ==> {"id": 1, "type": "subscribe_events", "event_type": "state_changed"}
[Debug] :  [Sending] ==> {"id": 2, "type": "get_config"}
[Debug] :  [Received] => Message type: result
[Debug] :  [Received] => Message type: result
[Debug] :  [Sending] ==> {"id": 3, "type": "get_states"}
[Debug] :  [Received] => Message type: result
[Debug] :  Parsing 41 Home Assistant entities
[Debug] :  Gethering views
[Debug] :  [Sending] ==> {"id": 4, "type": "get_services"}
[Debug] :  [Received] => Message type: result
[Debug] :  Parsing 20 Home Assistant service domains
[Debug] :  [Received] => Message type: event
[Debug] :  Parsing new state for sun.sun
[Debug] :  Settings change event: reconnect=true
[Debug] :  Socket connecting...
[Debug] :  [Received] => Message type: auth_required
[Debug] :  [Sending] ==> auth request
[Debug] :  [Received] => Message type: auth_ok
[Debug] :  [Sending] ==> {"id": 1, "type": "subscribe_events", "event_type": "state_changed"}
[Debug] :  [Sending] ==> {"id": 2, "type": "get_config"}
[Debug] :  [Received] => Message type: result
[Debug] :  [Received] => Message type: result
[Debug] :  [Sending] ==> {"id": 3, "type": "get_states"}
[Debug] :  [Received] => Message type: result
[Debug] :  Parsing 41 Home Assistant entities
[Debug] :  Gethering views
[Debug] :  [Sending] ==> {"id": 4, "type": "get_services"}
[Debug] :  [Received] => Message type: result
[Debug] :  Parsing 20 Home Assistant service domains

Why had I never thought of wearOS support for Hass!?
This would be great!

1 Like

I have Home Assistant 0.78.3
Now installed on my Huawei P10 HA Client 0.1.2. Aplha and i can not connect. I create on Home Assistant TOKEN for my Android but i can not connect…When try connect show me CODE 1… please help me.

This was reported already: https://github.com/estevez-dev/ha_client_pub/issues/6
If you don’t have default_view defined in groups.yaml, it will show blank. Will be fixed in next version.

1 Like