@TomTTFB

Devlog #7

This project has has so many issues from the start but adding the web ui has been the worst, I was trying to fix an issue which turned out to be my laptop for so long I forgot to devlog after it, so i ran over the 10 hour limit

The web ui is fully functional now, you can see all items and push them to the output remotely. you can connect the in game computer directly to the web ui over the internet or to the bridge server to the web ui

Devlog #6

I added a management app for AE2 spatial storage but i realised while making it that if you have AE2 installed the storage part of the program is useless since an ME system is so much better but the spatial manager is still cool i guess

Devlog #5

The search function and on screen keyboard are now added, i also reworked the requesting system, now you select items and add them to a queue, then it pulls the queue into the barrel instead of finding one item, requesting it then searching again and requesting

Devlog #4

This took longer than i thought it would but it turns out you cant move items to a container directly touching the computer, it needs to be connected using a modem but item requesting works now, you can choose an item, an amount and request it

Next to be added is the search function and a on screen keyboard which might also take a while but should be fun to debug and stuff

Devlog #3

You can now select items from the list by clicking on them and also items are seperated into pages instead of going off the bottom of the screen

Next job to do is actually requesting items from the chests to the output barrel below

Devlog #2

The debug screen now shows the connected devices along with other debug info like the total chests, time to scan and more

For now, the gui shows the item id formatted as capitalized with no underscores, getting the actual item name needs getItemDetail which was slow when i tried it so i need to find a way to speed the scan up or make proper names an option in the settings menu

Next ill work on the request system, the plan is to make each item selectable which will show a amount picker at the bottom and a request button which when pressed will push the amount of that item to the barrel

Devlog #1

I started by making a simple ui for the monitor and a debug info screen on the actual computer display. Next ill probably get some of the debug ui actually showing data and get a simple item list on the screen

Devlog #2
I added the last few features this session. you can Export and import as a tarball so you can move backups between machines or store them on a NAS, a diff view that compares any saved backup against your current config and tells you exactly which files have changed, and category-based partial restores (like appearance, panels, shortcuts, windows, and apps.) so you can pull back just your panel layout or just your shortcuts without touching anything else.

The CLI mode is also fully working so you can run pbm backup [name] or pbm restore [name] without going through the UI. it also makes a pre-restore snapshot so if something goes wrong you have a backup of a backup

Devlog #1

I made a bash script for backup and restore KDE Plasma configs. It has one command to snapshot all your Plasma files and one to roll back to the latest. This will be super helpful for when i was to play around with my desktop layouts and stuff without breaking anything permanently

Devlog #5
I think Token is at a point where I think it’s ready. USB HID works for typing codes, The web setup tool is done too, it handles adding accounts by QR code or manual entry, updating and flashing firmware.
It’s been fun building my first project for an ESP. Getting TOTP, BLE time sync, USB HID and the setup tool all working together took a lot of work but it’s good.

Demo:
https://i.tomttfb.com/vid/iwr6nx.mp4

Devlog #4
TOTP generation is working! The device is now showing real codes.

Getting here took more work than expected. TOTP sounds simple on paper but actually implementing HMAC-SHA1 correctly, handling Base32 decoding and making sure the time step calculation lines up exactly took a few attempts. I ended up getting help from Claude to do the implementation right but it works and now I understand how it fits together.

Next up is USB HID so pressing the encoder button actually types the code into whatever field has focus on the host.

Devlog #3
The UI is now functional The encoder scrolls between accounts and I added a full settings menu with brightness control, time sync options, and UTC offset.

Time sync is working over both WiFi and Bluetooth. WiFi NTP connects to pool.ntp.org and syncs in UTC automatically. The Bluetooth side uses GATT Current Time Service which is the same protocol smartwatches use to get time from a phone with no app needed. You just pair and the phone OS pushes the time automatically. The catch with BLE CTS is that it sends local time rather than UTC, so there’s a UTC offset setting in the menu to correct for this.

Codes are still placeholder 000000 until TOTP generation gets wired which will be in next devlog

Devlog #2

The main account list UI is looking good and it’s starting to look like a real product. It has the account name, email, and TOTP code laid out per row with the selected account highlighted. Placeholder 000000 codes for now since TOTP generation isn’t done yet, but the layout is exactly what I had in mind. The “hold side button 5s to power off” hint at the bottom is also working.

Also got carried away with designing UI and made the boot animation. characters rain across the screen like cmatrix with a key icon and TOKEN text fading in over the top before dropping into the account list. Small detail but it makes the device feel polished from the moment you turn it on.

Next up is figuring out how to get the time accuratly and actually generate TOTP codes on the esp

demo video: https://i.tomttfb.com/vid/39fpqg.mp4

Devlog #3
I got a basic web UI working, you can see your server list, create a new server and more. The core layout is there but its still minimal but it’s a real interface now instead oft just raw HTTP requests like last devlog.

The more interesting bit was getting the console output streaming to the browser in real time. You can now watch the server start up, send commands over RCON, and read log output live without refreshing anything. That was the piece I was most looking forward to building and it works well.

Demo video is here:
https://i.tomttfb.com/vid/boun6k.mp4

Devlog #1

Never done any Arduino or ESP32 development before so this has been a learning curve. Spent the first chunk of time just getting PlatformIO set up in VS Code and figuring out how the T-Embed CC1101 board works. lot of reading tutorials and LilyGo’s example code.

Got there in the end though with Hello World on the display in green with the RGB ring doing a rainbow pattern on the encoder. Small win but it means the toolchain works, the board is flashing correctly, and I can actually start building Token properly now.

Devlog #2

Core functionality is done. You can now create new servers, list all your servers, start them and stop them all over HTTP requests for now. No UI yet but ill probably do that next. Spun up a test server to make sure everything actually works correctly and it worked first try which was a nice surprise.

Next up is getting the console output streaming to the browser in real time, then building the actual web UI on top of what’s already working.

Demo video is up if you want to see it in action.
https://i.tomttfb.com/vid/7jpgdc.mp4

Devlog #1

Every existing Minecraft server panel I’ve tried is either massively overengineered or just unpleasant to use. Pterodactyl and Pelican are built for hosting companies to manage hundreds of servers, its way too overengineered for a home server. Crafty Controller is supposed to be simpler but I find it cluttered and hard to navigate.

I’m building something where you open the browser, pick a version, set a name, and have a server running in under a minute. An easy setup process, all configuration done through the Web UI, nothing complicated while still giving users full access to their server settings and files. Flask backend managing server processes, HTML/CSS/JS frontend.

The planning is complete. First milestone is getting a server launching and streaming console output to the browser in real time.