Agree that browser-mod is not reliable. Also, curious that FKB can turn the screen off. That would be a clincher for me.
It’s a low priority thing for me but it’d be nice to have more entity types in Android Auto… Like for example, the ability to turn on my home air conditioner and set a temperature when I’m in the car.
1 Like
Temporary workaround, use a script. We can probably add some basic support but Google only allows for simple on/off commands only so thats really where scripts come into play. Most likely a toggle for Climate can be added but setting temperature will probably require a script.
never said its impossible, just that our app does not have the permission in place for device admin. I am not sure on teh specifics of fully kiosk, maybe they already have that permission.
1 Like
Aha, understood…thanks.
Yes, when you add certain tablet into HA as fully kiosk integration you get quite some sensors, like screensaver, screen on/off, media player and some others. I have paid version, though, so i don’t know if all of these sensors also show in free version.
It is however extremly good idea to have fixed IP on that tablet.
This isn’t entirely true; look at how Nova Launcher turns off the screen. Device admin is one option, but the other way is to grant accessibility permissions and simulate a power button press.
2 Likes
Really hope the redesigned button widgets are merged soon, pls! lol Multi-action grid widget implementation by mrdanielps · Pull Request #4783 · home-assistant/android · GitHub
Yes the Zigbee 3.0 specification supports QR code device provisioning but most manufacturer do not make use of it, however the ZHA integration does actually have backend support a QR for a few manufacturers but there is no frontend support yet for Zigbee QR code
scaning the ZHA integration so today you have to use a different QR code scanner to decode it and them enter the QR code manually via ZHA actions. Again, for more details see this frontend feature request → Zigbee 3.0 device secure provisioning via QR code scanning for ZHA integration? · home-assistant/frontend · Discussion #12272 · GitHub
FYI, the ZHA integration actions (formerly known as services) only have qr_code support for QR Install Codes from these manufacturers:
- Aqara
- Bosch
- Consciot
- Embrighten
Also that this also requires a Zigbee 3.0 coordinator hardware with firmware compatible with Home Assistant as well as support for Zigbee 3.0 joining via install codes in the zigpy radio library, which so far is only supported in zigpy’s bellows and zigpy-znp libraries.
Services
Service zha.permit
To add new devices to the network, call the permit service on the zha domain. Do this by clicking the Service icon in Developer tools and typing zha.permit in the Service dropdown box. Next, follow the device instructions for adding, scanning or factory reset.
This service opens network for joining new devices.
| Data | Optional | Description |
|---|---|---|
duration |
yes | For how long to allow new devices to join, default 60s |
ieee |
yes | allow new devices to join via an existing device |
To join a new device using an install code (ZB3 devices) use the following data attributes (must use parameters only
from the same group:
| Data | Parameter Group | Description |
|---|---|---|
src_ieee |
install_code | The IEEE address of the joining ZB3 device. Use with install_code |
install_code |
install_code | Install Code of the joining device. Use with src_ieee |
qr_code |
qr_code | QR code containing IEEE and Install Code of the joining ZB3 device |
I was more curious because I’ve never seen it before with zigbee. In regards to development, it would need to be added in the core frontend before android could start development.
2 Likes
At the moment loading animation on first start is 2-stage one, maybe make it smoother and faster?
Understandable, but I was hoping it was a Play store specific issue. In any case, the devices should be just fine with whatever the ‘last’ version they support is.
Hopefully the releases on the GH downloads page will note when the API version is bumped.
It is an Android limitation. For example, with the current video playback feature, it only skips through a few frames because that is all that Android notifications support (not even a real video player).
iOS live camera feature also isn’t shown by default, only after a long press which is functionality that Android generally doesn’t have
1 Like
A few fixes available in latest Browser Mod v2.4.2 should mean that this is much more stable. v2.4.1 includes interaction requirement updates which is likely the issue Android users were having. v2.4.2 includes an update were brief disconnection may lead to no reconnection of Browser Mod sensors. Both these will have contributed to instability in the past.
1 Like
Thanks, that’s very good news. I’ll test it to see.
Yes that’s the plan we will add a note on the release.
Tried on my lenovo tablet and on my samsung phone , HA is not available as a launcher option …
One thing I’d love in a future version of the Android app is being able to use it as a Bluetooth Proxy, similar to how iOS can do it
1 Like
Really?
I did a search on Google for “home assistant ios app bluetooth proxy” and although we are not allowed to post it, the answer says that the app does not have this feature.
I quote (with the obvious risks here) :
That sounds more like iOS.
There’s a toggle in the app settings to set !
Excellent news that the project has a dedicated Android developer. Amazing what have been done so far without it!
I would very much like to see support for the application on my TCL Google TV. It would be amazing to have Home Assistant installed as an app on the TV so that people can use the TV to control the home and look at various dashboards.
TIA!
I tried looking up info about it as well, but I’m definitely not lying. I use an iPad Pro 2016(?) as my kitchen dashboard and one of my actual bluetooth proxies went unavailable so ironically I had to use the iPad to improv it back to HA