CubioShell

Your watch has a barometer, a thermometer, a heart-rate sensor, a compass, an accelerometer and a GPS. Right now they all report to the same place: a chart you never open. CubioShell hands them to you instead, the way a Unix box hands you its hardware. Every sensor is a file. cat /dev/baro reads the barometer. cat /dev/hr streams your pulse until you press BACK. cat /proc/sensors takes every sensor at once, and cat /proc/all adds your position to the same line, so where and what belong to one instant. A dozen sensors, three folders, one command. Then it composes. Pipe a device through sample 10 to take ten readings and stop. Pipe a file through stats 2 for the count, minimum, maximum and average of one column. Filter with grep. Redirect into a file that survives closing the app. And there is nothing to type: every token is picked from a wheel with UP and DOWN, so a whole command line is a few thumb presses. A line editor builds scripts from the same wheel, and sh runs them. A shell with no keyboard, written for a screen the size of a coin. That whole half is free, and it stays free. Install it, read your watch, write your scripts, keep your files. The paid half is the wire. post sends a reading to a hub. queue spools it on the watch for later, and sync, or a background worker every five minutes, delivers it when there is a phone in range. Harvest goes further: switch it on and CubioShell collects what the watch was already logging while the app was shut, pressure, temperature, heart rate and elevation, with the times they were logged, and delivers them without sampling anything extra. Your watch becomes a small, wrist-mounted sensor node that reports in on its own. Where does it send? Wherever you say. Three connection profiles each hold a base URL, a path, a body format and a credential. Point one at a hub you wrote and it speaks CubioShell's own envelope. Point one at Node-RED, Home Assistant, Ubidots or any HTTP endpoint that wants a JSON object and it sends named records, hr, baro, temp, with timestamps. Point one at a ThingsBoard device and it speaks ThingsBoard telemetry directly. Bearer, API key or Basic authentication, and a credential only ever travels to its own profile. There is no Cubio cloud in the middle, and nothing is collected by us. Some things it is honest about. It is not a safety instrument and not a medical device. It does not run your code: a script is a list of the same commands the prompt offers. And a watch shows only the sensors it actually has, so a quiet sensor reads as quiet rather than being invented. Requirements: a Garmin watch with Connect IQ 3.1 or later. Anything that leaves the watch needs the Garmin Connect app on your phone. Reading the watch itself needs nothing at all. Install it for free, play with it, and when you want your readings to leave the wrist, the license is one activation code, entered once, bound to your watch, offline forever after. No account, no subscription. Get the license, the manual and the ready-made ThingsBoard rule chain at https://shop.cubio.no/p/cubioshell.html

1.0.111 Bug fixes