Hello to all
any app that can easily be used on a android media box (those ones linked to TV) ?
also maybe for samsung TV…something on the way?
thanks
Hi All, I was using HA_Client with on my local network (192.168.##.###) and on cellular network (duckdns.org) on HTTP (HTTPS to OFF), everything was fine.
Today I install SSL protocol with Letsencrypt. Now I’m only able to connect with LTE, when I’m on my local network the client dont want to connect. On the app log i have an error
[Error] Socket stream Error:
WebSocketChannelException:
WebSocketChannelException:
HandshakeException: Handshake error in client
(OS Error:
CERTIFICATE_VERIFY_FAILED: Hostname
mistmatch (handshake.cc:352))
Is someone can help me with that?
Thanks!
Are you able open your web UI the same way you are trying to connect HA Client?
Yes with chrome i’m able to connect with the same IP adress using https
But chrome mentionne there à problem with https or something like that…
https://###. ###.###.###:8123/auth/authorize?response_type=code&client_id=https%3A%2F%2F###. ###. ###. ###%3A8123%2F&redirect_uri=https%3A%2F%2F###.###.###.###%3A8123%2Flovelace%3Fauth_callback%3D1&state=eyJoYXNzVXJsIjoiaHR0cHM6Ly8xOTIuMTY4LjIuMTc1OjgxMjMiLCJjbGllbnRJZCI6Imh0dHBzOi8vMTkyLjE2OC4yLjE3NT…
Ah, so unfortunately you SSL certificate is generated for your domain, not IP address. And currently it is not possible to connect with invalid certificate.
Hi, I have two questions:
First, is when I toggle Use Lovelace UI, I get “Error getting lovelace config: No config found.” I have no idea why this is happening. Leaving it off everything works perfectly.
Second, I have some mdi icons that are showing in the web console that are not showing up in the app. Could this be the app needs to have a newer version of the mdi icons embedded?
This app is really great! Thank you!
Hi @majorsl
If the app says “No config found” it means you don’t use Lovelace UI at all. Just leave it off.
If there are some icons not showing up in the app, it indeed means that I forget to update icon library in the app. Will fix it in next release, thanks for pointing.
Thank you for the reply. I was under the assumption that Lovelace is the default UI. I’m new, still learning.
1 Like
Hi all.
I’m happy to release HA Client 0.7.0 with location tracking, tablet UI and some love for media_player.
See full release notes here: https://github.com/estevez-dev/ha_client/releases/tag/beta%2F0.7.0
Get the app here: https://play.google.com/store/apps/details?id=com.keyboardcrumbs.haclient
5 Likes
Nice! Thanks for your work on this.
This is excellent! I have not used location (GPS) tracking with HA before and am fairly new to it so am excited about this. I have a question though, I have location tracking turned on in the HA Client app which works great, but it only tracks location and battery etc while at home on the wifi network. Once I leave home and its on mobile network it wont report anything. What else do I need to configure for location (GPS) tracking on mobile network? I have the device_tracker entity created and a nabu casa subsciption also
Do you able to use the app outside of your home network? I mean could the app connect to your Home Assistant from outside?
the HA Client app itself wont work away from home but the remote control link for nabu casa works. The app connection settings are standard IP address ie 192.168.1.xx, port 8123 and HTTP
So how the app should send data home if you are using local IP in it?
You can use remote UI url in the app as well
OK, this is where im not understanding correctly. In connection settings does the remote URL go in the ‘domain or IP address’ section and leave port blank?
It is correct
I’ve set up the app and love it. But. The location function stopped updating for me on 29/10/2019 at 4:04pm.
I’m using a Pixel 3 - Android 10. I allowed location permissions to ensure it should still be sending but no updates since that time. Anything I can check?
Placed remote url into ip address section, it auto filled port to 80. Got error getting states 'HA Error". Tried it with wifi on/off, port 80 and 443, still same error.
Use remote UI url without protocol and pages. If it is https://6offfkflflgeogege.ui.nabu.casa/lovelace/0 then use 6offfkflflgeogege.ui.nabu.casa in address field. Use port 443