Itâs rarely about the hardware but rather if there are drivers available. Same as with old iOS devices. Somebody decided I it ainât worth it anymore. Thanks to CM / lineage lots of very old devices still got her Android versions.
I agree setting a limit on 4.4 is reasonable. Webview is too much effort, all other issues should be solvable.
my tablets have 4.4.2 so i am save when the line is set at 4.4
and if i had the option tu upgrade android, i probably would, but its a cheap tablet and they dont give that option, so i am stuck with 4.4.2
not that i am sad about that, because 4.4 is not a bad version anyway in my eyes
Ok, Iâve posted an APK to try. It should still be feature complete! The jsExec example will not work if it needs to create a dialog I think (quick search says its a bug), at least it doesnt in the emulator. But it will still work on Android 5.0+
Note to anyone using an older copy, a number of the preferences have been renamed to make everything consistently named, so you may need to set them again (eg, default URL and MQTT enable)
Very happy to see this install on the cheapie tablets I bought for home assistant control/display. They are Android 4.4.2, I sent hours online last night trying to figure if I could update them to Android 5, no luck there.
Now strange thing, the browser gets to the homeassistant front page and asks for a password, which I donât have set. It wonât go any further.
I honestly never actually pointed this at HASS, since I am using HADashboard v2, so I didnât go too deep into the browser side yet. I can verify side by side right now that a newer version of Android goes in fine to my HASS but the API19 version has the same behavior you are seeing
Iâll dig into that tomorrow, since its just about bedtime here. My hunch is that thereâs some feature around websockets that is broken right now.
Question for you, if you use the default OS browser to hit HASS, does it have the same behavior or does it work?
Tile is still at top right after I changed my dash file to move it to the bottom row. Refresh in firefox shifted it, but it is still stubbornly top right in homedash even after a reboot. Caching problem?
Interestingly iframe seems to appear correctly on homedash.
On 4.4 you should still have the same rendering engine in the webview so thatâs really weird.
On your desktop chrome you can connect the remote debugger to see the webview error console, maybe that gives a hint.
On the Android 6 tablet in front of me âAndroid system webviewâ has version 56.0.2924.87 is that the same for your tablets?
Hi which camera is motion detection configured on by default? Appears motion on front facing camera is not triggering the display and I donât see an option to set which camera to useâŚ
To my pleasant surprise the motion detection works even with the tablet behind some cheap two way glass, so I can place it in a âsmart mirrorâ setup
Another suggestion for this project, could a wired keypad attached to the tablet be used to send MQTT to HA? My idea is to have the tablet embedded in the smart mirror, then have the keypad disguised in the mirror frame so I could toggle switches using a physical button
@quadportnick youâre a genius!
This is a great addition to the hass universe. Very cool.
Working-ish on my galaxy tab 7, android 4.4.2
Motion detection and browser working, hass url not loading (buffering/loading indefinately), google and various other pages loading fine.
Mqtt not seeming to send though - listening on my mqtt server (hass AiO mosquitto) and thereâs nothing coming in. Is there a particular method to getting mqtt working or shold it work out of the box?
Again, great work
Edit - my bad, i didnt read the bloody thread properly - @ray0711 thankyou so much