In theory yes, but we don’t have any instructions for starting over with a clean raspbian.
At some point I expect that we will have a guide that lets you install it on most distributions, but we are not quite there yet - to achieve this, for one, we will need to create an installable package with all the low level power management services, so I don’t think it’s something that we will work on in the near future.
We of course welcome all contributions, so if you do decide to investigate the provided image, we’d love to hear about it. (Most of the logic is located in /var/cache/salt/)
Thanks for the pointer: I am not familiar with the salt stack tool-chain, so I think I’ll pass for the moment being ;-).
I’ll start using the pre-cooked image to familiarize with the dongle features.
PS. I’ll keep monitoring this thread in case somebody from the community is interested in joining forces to make some deb packages to freshly install on a new raspbian.
I’m happy to work on this with you and come up with installation scripts to replicate all the needed configuration. No background with salt stack tool-chain but there’s always something to learn!
At the moment we dont have instructions for a clean install, so you are still (unfortunately) on your own here. However, I do recommend that you flash the current image and then take what you can from this. It will give you a good head start. Once the device connects to the AutoPi Cloud, most of the configuration will be downloaded from the cloud, so you’d only need the basic functionality to get the device working.
I notice that there is a deploy.sh script in the root of autopi-core. I am fairly familiar with salt as I use to manage my various home computers. Is all the autopi functionality contained in this repo - at least as far as getting started?
Update on this. It starts, but the pi shuts down before the salt minion completes its highstate.
ISTR there are sensors that shutdown the pi if the engine is not running. In my case, I’m running on the bench using the approved 12V supply plug (currently at 13.6V).
I know I can disabled the timers that cause this shutdown, but not until after the UI is installed - Catch-22!
I’m very invested in this topic, as I feel I have just made a mistake in purchasing this device. My ultimate goal was to create an automobile entertainment system with an amp capable of driving the speakers, and a GUI capable of managing media files. I purchased the Autopi in the hopes that it would add ADDITIONAL telematics functionality to my set up that I could use to make widgets and what have you… After scouring this community and reading several threads, it is seeming more and more likely that I’ve gone in the wrong direction.
I really hope that you are able to get a full OS working on your rig that also allows you to operate the Autopi functionality side by side.
I’ve tried to start from a baseline of raspbian stretch, restoring my salt config, installing salt-minion and kicking off a highstate. I’ve tried with the 2019.2, 2018.3 and 2017.7 minion releases. All fail.
V2017.7 fails due to missing features specified in the state files (specifically the tojson filter, which came in V2018.2).
V2019.2 fails because the sls specify features that were removed in V2019
2018.3 gets the closest but right at the start, the highstate tries to patch salt-minion.py and fails because of a checksum error.
I can only assume that autopi based their efforts on a version of the salt-minion that is not available anymore.
How sad. It’s a shame that the Autopi cannot be be easily integrated into other projects. It seems it is designed to be the base hub, and projects should be built around its limited functionality