Now I'm in hotel not train I fiddled with last nights #tildagon problems:

WiFi.scan only returns the access points it sees when it's connected to its configured network, not when it is out of range of its configured network. Change the config to my phone hotspot and it can see everything around me again.

USB works again now I physically wiped down, blew into, and pressed hard onto the board. So I guess something sad happening around the connector.

I don't normally get #GPS inside ICEs, including the last one, but I'm standing in the cafe of this one with my #Tildagon data logger and the little green LED has been blinking more than half the time. I havent looked at any geographical interpretation of what it is recording. These cafe carriages have funny roofs though.
So my tildagon sees loads of WiFi networks in my apartment building. But not in the bar and not in this train. Both of which my phones can see. All very suspicious. #wifi #tildagon co2 is 700 btw.
Pimoroni breakout garden attached to #tildagon... First outing: it's pretty easy to knock breakouts out when swinging shit around in the real world. Like 3 times in 10 minutes. My badge doesn't see the WiFi in my local bar. But it does see the #CO2. #GPS tracking LED stopped flashing right as I walked through the door which is what I expected.
Welp! Day 604 of #EMFCamp 2024 already... #tildagon #BadgeLife

Ok, so, I’ve spent since November screaming at toasters (AI) to try and get my #tildagon app working.
It’s entirely vibecoded (like, 150%, it gives me code and I throw it on, not even a brief check over) & so far I’ve learnt:
1) if it doesn’t work on the simulator, it may work on the badge regardless.
2) the only ai agent that made any headway at all was Claude.
3) useless github release notes are fun to write.

App is called Badgagotchi.
Don’t install it, I wouldn’t if I don’t have to.

I have some #Pimoroni #BreakoutGarden sockets that I'm wiring onto a #Tildagon #Hexpansion because I have a few breakouts I'd like to use.

#I2C pins are obvious, but the connector has an ambiguous additional pin that is different on every board.

I guess I'll wire each one to a separate Tildagon GPIO. Which kinda de-generalises having everything on one i2c bus. (some boards its an interrupt out, some its a trigger in, on many its unused)

What do their official #RaspberryPi boards do here?

Made my #tildagon event sequencer app have a "play in background" so you can do other stuff while it runs, made it respond to the IMU detecting the badge is upright, gave it basic infinite loops. It's still not usable but I have way more than I expected after so few days.

ok, I implemented my #Tildagon "Emotion Events" idea - there is:

i) 3 line patch to firmware to add Positive and Negative events for when something Good or Bad happens in your app that you want the rest of the Tildagon to know.

ii) 3 line hack to Snake to send positive events when you eat food and negative when you hit a wall

iii) a driver that flashes the back LEDs green or red on events.

Next steps: make my piezo add on bodge play happy and sad tunes; make the built-in apps fire events.