> For the complete documentation index, see [llms.txt](https://docs.motus.org/sensorgnome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/sensorgnome/appendix/software-history-and-why-v2.md). # Software History and why V2 * The original Sensorgnome software was written and maintained by John Brzustowski from 2016 to 2018 and was designed for Beaglebone and Raspberry Pi models 1 and 2 single board computers. It used an ingenious but very non-standard "liwixi" filesystem organization and was based on Linux Debian Buster. Communication with Motus servers used SSH tunnels in an effective but unconventional configuration. * The Sensorgnome V2 software is a complete rewrite of the system with the goal of supporting current Raspberry Pi models and using standard filesystem and communication methods. * The V2 software: * uses a standard current Raspberry Pi OS image (based on Debian Bullseye as of 2023) that has Sensorgnome software pre-installed * runs on Raspberry Pi3, Pi4, Zero-2W, and SensorStation V1 (more coming) * exclusively uses HTTPS for Internet communication (SSH commandline access over the LAN is also supported), * implements a new automatic upload mechanism that uploads data files directly to motus.org, * implements a new web UI with more functionality and security to manage the Sensorgnome, * the new web UI provide easy options to download data files to a laptop or phone, * implements remote monitoring and management, * The V2 software uses unmodified software to process radio data and detect tags in the local tag database, thus the data processing path is unchanged. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.motus.org/sensorgnome/appendix/software-history-and-why-v2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.