I didn’t configure anything really, I just launched the app with it (you need a full path): daemonize /data/data/com.termux/files/home/hass/bin/hass
It seems to work so far, I haven’t really wondered more to be honest and I haven’t checked how it launched with the venv, I just did the usual source hass/bin/activate before. Though I assume that if something was not on the venv it would have taken much longer to launch.
Hi, has anyone been able to install the latest version with termux? what packages have you used (nexus 7) or what version of HASS and packages are correct? i am using LineageOs 18 (Android 11).
For the record, I’ve just updated to 2022.4.1 without issues on upgrade. That said, I got issues with PyNaCl when starting, not finding ld in the path for some reason: checking for ld used by aarch64-linux-android-clang... no
@Ritual I have not encountered errors related to this package.
Do you have more details about the error, a longer log message perhaps? Also, try to give more details on your configuration (tablet, system, etc)
I was trying to install it on oneplus x.
I wanted to try before i buy a raspberry and install on it.
But with no luck.
I tried it on lineage(Android 11) and rr remix Android 7
I got many different errors on both those roms.
I got the previous error which i posted from the playstore version,which got resolved once i downloaded the apk from github.
I got many errors after that and i tried resolving it for few hours and ultimately gave up.
Thank you tho.
Can anyone reply with a sequence of codes which are confirmed working.
Because there are many different sequences in the comment section and the main sequence/versions don’t work for me.
It would really mean a lot.
And please state the os and Android version aswell.
Now you don’t necessarily need to install python manually the same way, but most of the dependencies are there. After, it’s a bit of a mess because installing this way is not trivial. You run in a lot of dependency issues, and with the added difficulty of the rare architecture. General packages are rarely built/tested to run on an android tablet. So you have to take it one error at a time, solve it, and solve the next one that arises.
If you are interested in continuing this way, try to post the actual errors you encounter.
Otherwise, if all you want is a quick test until you potentially get a dedicated device like a Raspberry, I would suggest a more straightforward setup, like a docker deployment or a VM. Might take more time to prepare, but at least it will install without issues.