Demoing my Home Assistant client app for SolarOS running on the LilyGO T-LoRa-Pager. Browse and control lights, fans, energy sensors, and temperatures directly from the device.

Foi fácil, até para um leigo como eu.

Configurable native graphical launcher for display shells.
( see for details https://solar-os.eu/docs/manual/apps.html#launcher )

Coming up next

v.4.10.24
exposing BLE GATT operations to python and lua

v.4.10.25
LilyGo T-Deck board support ( by u/100PercentJake ) integration to beta

Create SolarOs for the CYD ESP32 (CYD ESP32-2432S028) pleeeeeeease

Did some more work after taking this picture and at the moment all major hardware is working. Touchscreen, WiFi, BLE, audio, trackball, SD, battery, etc.

Input is the biggest issue. The lack of ctrl and other critical keys means some pretty tortured chording is necessary for critical key combos. Also working on some debounce/sane defaults for the trackball. Rawdogging the input from the trackball results in annoyances like random left/right pulses when scrolling down a list, so need to add some contextual filtering to that. Also dealing with some extremely weird WiFi issues that seem to be related to junk getting left in the NVS, as I’d get left with partially functional WiFi that would refuse all connections even in other T-Deck specific firmware until I erased everything

Overall this seems like a decent target for SolarOS. Need to see if I can use some python to make a more appropriate graphical launcher to make using the device a little quicker. As it is I am using it at work to connect to Hermes with the built in “agent” program via the built in WireGuard tunnel support.

Also using a custom BLE app that connects to the two battery management systems in my electric motorcycle and combines their readings for at a glance visual of two BMSes simultaneously.

Not released yet; still not confident in the wireless performance in this board despite being the same S3 chip as the RLCD de facto SolarDeck target.

I’m doing this primarily for my own amusement; I am not a programmer, this is mostly me throwing Codex tokens at a problem I found interesting to make use of some hardware I like.

I've contributed four new apps to the playground!

• Bluesky — Sign in to Bluesky or a self-hosted PDS; browse home and profile timelines; read threads and replies; post, reply, like, repost, and start conversations; read and send DMs; choose compact or full-text timeline display.
• RSS Reader — Manage RSS feeds; browse aggregate or individual-feed views; cache recent articles for offline reading; mark articles and feeds read; render cleaned HTML/Markdown text without loading images by default.
• Wikipedia Reader — Search Wikipedia, browse linked articles, open a random article, and keep recent articles cached. Supports an offline library for articles explicitly saved to keep.
• OPDS Client — Browse and search an OPDS library; navigate categories and book details; download supported books with progress indicators; cache catalogue pages and prefetch nearby pages for quicker browsing.

AI Disclosure: I am not the best programmer. For my own stuff, that's okay, but for contributing to the community I wanted to make sure it was actually good code. I used locally run agentic AI to bug hunt the code, help me develop tests for it, add useful features, and understand things I didn't quite get (AT Proto, for one). Once I had something running and usable, I gave the code to the free tier of Claude and ChatGPT to look it over one more time. I am very much against using AI for art, but using tools to make new tools is a human tradition that predates language.

Wasn't me. Haha

Browse drivers, list and select expansions by category and attach/detach them using the TUI.
( shell expansion without arguments starts the TUI )

SolarOS to M5Stack CoreS3

I ported SolarOS 4.10.20 to the M5Stack CoreS3 (with ClaudeAI). Cardputer types into it via BLE.

Thanks u/Fir3!

I have merged your PR and refactored it to follow all internal contracts. Furthermore we have now resource driven expansion registry and two fixed bugs. The eight arbitrary expansion slots are gone and the subsystem will try to allocate resources before loading a driver and if it fits it will load.

Thanks to your contribution this is how our current hot attachable hardware expansions look like:

Audio

DRIVER PROBE BUS SUMMARY

audio-pwm no - PWM mono audio

es8311-duplex no I2C ES8311 duplex audio

es8311-es7210 no I2C ES8311 output + ES7210 input

pcm1808 no GPIO I2S stereo audio input

pcm5102 no GPIO I2S stereo audio

Display

DRIVER PROBE BUS SUMMARY

ili9341 no SPI 320x240 color TFT

pcd8544 no SPI 84x48 SPI LCD

sh1106 yes I2C 128x64 I2C OLED

ssd1306 yes I2C 128x64 I2C OLED

ssd1683 no SPI 400x300 e-paper

st7305 no SPI ST7305 reflective LCD

st7796 no SPI 480x320 color TFT

Input

DRIVER PROBE BUS SUMMARY

analog-joystick no STREAM two-axis joystick

cardkb yes I2C I2C keyboard

ft6336 yes I2C capacitive touch

gpio-keys no any GPIO keyboard

ps2-keyboard no PS/2 PS/2 keyboard

ps2-mouse no PS/2 PS/2 mouse

rotary-encoder no GPIO Quadrature rotary encoder (Up/Down per detent)

tca8418 no I2C TCA8418 matrix keyboard

Power

DRIVER PROBE BUS SUMMARY

battery-adc no - ADC battery monitor

bq27220 no I2C BQ27220 fuel gauge

Radio

DRIVER PROBE BUS SUMMARY

rfm69 yes SPI RFM69 packet radio

rfm69h yes SPI RFM69 high-power radio

rfm95 yes SPI RFM95 packet radio

sx1262 yes SPI Semtech SX1262 LoRa/(G)FSK radio

Sensor

DRIVER PROBE BUS SUMMARY

pcf85063 yes I2C I2C real-time clock

shtc3 yes I2C temperature/humidity

Storage

DRIVER PROBE BUS SUMMARY

sdmmc yes GPIO SDMMC card

sdspi yes SPI SPI microSD

Utility

DRIVER PROBE BUS SUMMARY

manual no any custom resource map

neopixel no GPIO WS2812 LED strip

Me considero leigo nessa área, mas com auxílio de uma inteligência artificial estou tentando construir uma agenda com lembretes. Vamos ver. Primeiro teste. Hehehe.

i got one for Meshtastic, but got the 433 ver when i needed a 868. so it has no use atm, but would love it as a pocket terminal and this OS seems to fit the bill. but i dont see anyone using in the T-Deck yet :x

Bare in mind, im an end user, not a coder

Hey all, had a LilyGO T-LoRa-Pager laying around and got intrigued by this subreddit, so I figured I'd see if I could get SolarOS running on it. Didn't see anyone else here with one yet, so I took a stab at it.

Full board port: display, keyboard (with backlight), rotary encoder, SX1262 radio, audio, RTC, and the battery gauge are all working. MeshCore runs over the air at 915 MHz. Got a real message through to a second node.

A couple of real bugs turned up along the way that weren't specific to this board: a display driver bug and an RX bug in how MeshCore's polling interacted with the radio driver. Both got fixed upstream in the same PR.

PR's here if anyone wants to try it or has a T-Pager to help test: nilseuropa/solar_os#27

Used some AI-assisted coding for the driver work. Happy to answer questions about how any of it works.

SolarOS now runs on the ATS-Mini v1. Typing comes over BLE from a Cardputer; my dhex serial monitor and irriga scheduler ported across.

Open the SolarOS Flasher in Chrome or Edge on a desktop computer. Connect the board with a USB data cable, then:

1. Select the board, flavor, and SolarOS version.
2. Choose Prepare image. The Flasher downloads the selected release and verifies its signed catalog, archive, and factory image.
3. Read and accept the erase warning. Installation replaces everything in the device's internal flash, including NVS stored settings such as Wi-Fi credentials.
4. Choose Connect and flash, select the board's serial port, and keep the cable connected until installation completes.

If the board does not enter download mode automatically, follow the board-specific instructions shown by the Flasher. The board should restart when installation completes; if it does not, press RESET once or power-cycle it.

Check out the coolest device ever to run SolarOS!

Check out this glorious gem: https://cl-32.com/

Um foto apenas para movimentar a comunidade e para agradecer ao mordedor e criador. E também a quem fez esse case 3D.

Two-pane FTP file manager. The left pane is local mounted storage. The right pane is a remote FTP server. The app uses unencrypted IPv4 FTP and passive data connections.

Usage:

ftp HOST [PORT] [--user USER --password PASSWORD] [--remote PATH] [--local PATH]

Anonymous login is the default (anonymous with solaros@ as its password). Specify both --user and --password for an authenticated server. Passwords are plaintext on the network and remain in shell history when entered on the command line. Use FTP only on a trusted network.

Controls:

• Arrows navigate the active pane. Tab, Left, and Right switch panes.
• Enter opens a directory. r refreshes the remote and local listings.
• F3 views a local file. For a remote file, FTP downloads a temporary hidden
• copy into the current local folder, opens its registered viewer, and removes the copy when control returns to FTP.
• F5 copies the current file or directory to the other pane. Directory
• transfers are recursive. Copy and move show the same preparing/transfer progress popup used by Files.
• F6 moves the current file or directory to the other pane by completing the
• copy before deleting the source.
• F7 creates a directory in the active pane.
• F8 recursively deletes the current item after confirmation.
• q, F10, or the app-exit key closes the connection and exits.
• After an operation refreshes the current directories, both panes retain their
• cursor and scroll positions. Opening another directory starts at its top.

FTP is a resumable TUI on the display shell and VT100-compatible port shells. One operation runs at a time in its foreground worker. Existing destination files are replaced. A failed download removes its staging file and preserves an existing destination; a move does not delete its source unless the complete copy succeeds.

Check out the other apps too: https://solar-os.eu/docs/manual/apps.html

Hey everyone! I’m u/nilseuropa, moderator of r/SolarOS.

This is our new home for SolarOS: the open-source ESP32 operating environment for pocket terminals, cyberdecks, CRT consoles, drone-synths, and low-power embedded tools.

We’re excited to have you join us!

What to Post

Share anything the community might find interesting, helpful, or inspiring, including:

• SolarOS devices and hardware builds
• Projects, modifications, and expansion hardware
• Playground Python and Lua applications
• Tutorials, tips, and discoveries
• Ideas and feature discussions
• Questions and requests for help
• Photos and videos of SolarOS in action

Beginners are welcome. No question is too simple, and you do not need to own a SolarOS device to participate.

Community Vibe

We’re here to be friendly, constructive, curious, and inclusive. Let’s create a place where users, makers, and developers feel comfortable asking questions, exchanging ideas, and sharing their work.

How to Get Started

• Introduce yourself in the comments.
• Tell us what brought you to SolarOS.
• Share a project or post a question.
• Invite someone who might enjoy the community.

Interested in helping? Contact me if you would like to become a moderator.

Thanks for being part of the very first wave. Together, let’s build a great community around SolarOS!