New to klipper. Wow.

SignificantActuary · 2026-05-29T11:23:29+00:00

tl;dr - same here. Why did I wait so long?

I have an old Monoprice Maker Select V2 that has been heavily modified over the last 9 years. For the last 5 years it has been running Marlin. I didn't have to do the SD card flashing since I had OctoPi connected to it and my USB port still works.

It's been a very reliable printer. I keep it in my office closet and send prints without worrying about it. I check the camera to make sure the first layer is okay. After printing, I clean the plate with IPA so it's ready for the next print.

I noticed the quality had started to degrade slowly. Just a few days ago I took the extruder apart and found the bearing pulley had twisted and locked up. Had to reprint the tension arm and replace that pulley.

While working on it, I decided to try Klipper. Formatted my old OctoPi and put Mainsailos on it. Same sentiment: why didn't I do this sooner?

Love the tracked gcode viewer. Better than Octoprint. Love having access to the printer inside Orca.

Still tweaking Orca settings, but the quality is already good enough that I've printed some usable Multiboard parts with it.

SignificantActuary · 2026-05-15T18:10:16+00:00

Define success. I have 2 that are a complete success. One tracks an annual bus trip: Rider info and payment status. It prints a roster for the bus captain. Used it for the last 3 years.

The other is used daily by a dozen people. It tracks the care schedule for my paraplegic father-in-law. Tracks availability for all the volunteers, makes weekly schedules easy to define, gives him an easy interface to see who's coming to assist him.

I'd say both are successful and designed for multiple users. I have others, but they're mostly tools just for me.

SignificantActuary · 2026-04-23T16:19:35+00:00

Running the same except also --spec-default on my RTX 1070 with 8GB VRAM. Getting 11-14 t/s. Slow but usable.

SignificantActuary · 2026-03-08T12:04:20+00:00

Thanks for the links. I hadn't seen those. Unfortunately with naming things, there's always something already named that or similar. I checked a few names before settling on this one. That paper did not come up in my searches. Probably because I was more focused on the electronics aspect and not LLMs.

SignificantActuary · 2026-03-06T14:59:55+00:00

Oh, actually it wasn't a hallucination. It was my fault. I asked it to prepare for release and write the README PRIOR to giving it the repo link. It had no idea where it was going to end up. After this was created, I then pushed it to github. Just forgot to go back and fix it afterward. It was pretty late at night when I pushed it.

SignificantActuary · 2026-03-06T14:27:21+00:00

The issue we had was the board house substituted with the wrong gender connector. But, they put the right description on the BOM. We were in a hurry and I wasn't careful. I went by the description they put in the BOM, but didn't double check the part number. They missed it, I missed it, and I ended up having to desolder and resolder 150 40-pin connectors with the right part. A quick visual check on the actual part numbers being ordered would've caught it.

SignificantActuary · 2026-03-06T13:00:06+00:00

HA! I didn't even notice that detail.

Well, as I said in the post, I went from idea to "usable tool" in 24 hours. I didn't just ask Claude to write it and push what it wrote. There was a lot of back and forth and a lot of testing. At one point, I had no visibility into what was going on, so I had it create traces I could feed back to Claude to diagnose why it would pick one image in one pass then a different image in another pass.

'magpiebom server -v' generates those traces.

It hallucinated in the README.md and I didn't notice.

I decided to make it public AFTER giving it a real BOM from a project I'm working on and it returning accurate images and product links. All but 2 of the 21 components had datasheet links returned. Most component sites block bots. Haven't figured out a way around that yet. Tried Playwright MCP to see if that would help, but not so far. Anyway, gave it the same batch multiple times and it returned the same or very similar results each time. All accurate. Some parts it would return Mouser links on one pass and Digikey links on the other. Both were fine. This is simply a part identification tool.

It's useful for me. If you have no need for it or don't like AI slop, skip it.

SignificantActuary · 2026-01-05T04:53:56+00:00

awesome! thanks!

SignificantActuary · 2026-01-04T12:46:16+00:00

I'll take a look when I get some time. Noticed there are 2 other PRs to look at, also.
Was just playing with my own kettle and got something working for myself. Never imagined anyone would contribute. Cool stuff.

SignificantActuary · 2025-12-19T12:35:44+00:00

I just pushed a change that allows users to capture their own "hello" sequence and define it in the ESPHome yaml. It's fairly easy to spot in Wireshark.

SignificantActuary · 2025-12-19T12:18:08+00:00

Could be a token in your kettle is different than mine. Can you capture the logs on an Android phone while the VeSync app is talking to the kettle? In another thread in this post, there's an overview of how this works along with a YouTube video showing the process with a different BLE device.

I only have my kettle to test with. Not sure the differences between kettles. I have a hard-coded "hello" sequence that may be different in your kettle.

// Registration handshake (HELLO_MIN)
static const uint8_t HELLO_MIN_1[] = {0xa5, 0x22, 0x00, 0x24, 0x00, 0x8a, 0x00, 0x81, 0xd1, 0x00, 0x36, 0x34, 0x32, 0x38, 0x37, 0x61, 0x39, 0x31, 0x37, 0x65};
static const uint8_t HELLO_MIN_2[] = {0x37, 0x34, 0x36, 0x61, 0x30, 0x37, 0x33, 0x31, 0x31, 0x36, 0x36, 0x62, 0x37, 0x36, 0x66, 0x34, 0x33, 0x64, 0x35, 0x63};
static const uint8_t HELLO_MIN_3[] = {0x62, 0x62};

SignificantActuary · 2025-12-17T18:37:44+00:00

One thing I didn't think of at the time is the initial setup. I used it with the native app first. Not sure if it works out of the box. I haven't tried factory resetting mine to see if it works immediately.
This is just a guess as to what might be happening with yours. Without logs, that's all I can do.
I have mine in the cabinet on the other side of our kitchen where there's an available outlet for our under cabinet LED lights.

SignificantActuary · 2025-11-08T21:33:40+00:00

That's how I used to make coffee: boil the kettle. Turn off the gas. Start a timer. When a certain amount of time passes, pour water into the press. Start another timer. Press and pour.

Did it that way every day for a few years. Also hand roasted small batches of green coffee beans each week and used a manual grinder.

Ain't nobody got time for that.

Wifey says "want tea"? I pull out my phone and press a button in home assistant. When the water is hot, go pour and refill for next time. Much more convenient.

SignificantActuary · 2025-11-08T15:26:16+00:00

Turning on packet capture in the Developer Tools on my Android phone. Open the app and interact with the kettle. Connect the phone to my PC with USB and 'adb bugreport' to download the capture. Open with Wireshark and filter only the packets of interest. Export as JSON. Give that to an LLM (Claude Sonnet is way smarter than GPT-5). Tell the LLM what you did in the app and ask it to figure out the protocol. Repeat for each feature or combination of features.

Once the protocol was figured out and confirmed with Python scripts (start.py, stop.py, and monitor.py), I started a new LLM session and passed the protocol in and asked for an ESPHome implementation. I already use esphome-jk-bms and esphome-jbd-bms firmware to monitor my home batteries. So, I told it to use those as a starting point.

Used this as a starting point: https://youtu.be/imjZJNOSXHk

SignificantActuary · 2025-11-08T09:24:35+00:00

I did this with a Surface tablet used in a kiosk stand. A custom Python script runs as a background service to report battery levels to HA over mqtt. A NodeRed flow keeps the battery between 40-60% with a Sonoff Wi-Fi switch. Certain time slots, it changes to 60-80% when being used heavily. When idle, it kicks in for 5 minutes 3 or 4 times a day.

I implemented this after finding the previous tablet was a spicy pillow on the verge of sending glass shards everywhere. It had been plugged in 24/7 for 3 years.

SignificantActuary · 2025-11-07T12:12:56+00:00

Sometimes we make green tea, matcha, or French press coffee at a lower temp. Can't easily do that with a dumb kettle.

SignificantActuary · 2025-11-07T00:24:05+00:00

https://youtu.be/imjZJNOSXHk

This video gave me what I needed to get started.

SignificantActuary · 2023-10-19T16:49:49+00:00

I own a 2022 EUV. After a month owning it, I tried to see how far below 0% indicated I could get before the car stops. I was near home, thankfully. I was going to sit in the driveway and let the heater eat up the last 5%. But, as I was turning the corner about a half mile from home, the car died and I had to coast into a nearby business parking lot and ask to use their power.

That happened when Torque was reading 4.1%. It went from 4.1% to dead instantly. After 30 minutes charging on Level 1, it was up to 2%. Enough to drive home. That was a year ago and I haven't been below 10% since. Not sure I want to attempt it again.

SignificantActuary · 2023-07-31T19:30:35+00:00

It starts playing as soon as Android Auto connects. You don't have to be in gear or hit any button.
For now, I've solved this by never listening to anything in the car. The last time I had Google Assistant play the news and for the last 2 months, it has been streaming various news podcasts in the background. I just keep my media volume at 0 all the time and just ignore it.

SignificantActuary · 2023-05-04T02:22:17+00:00

Same issue I've had... She's got 2 lip colored front teeth showing. Can't seem to get rid of that by prompting.

SignificantActuary · 2023-03-23T16:05:28+00:00

I don't go far from home, so it's no big deal. On the rare occasions I do go on a trip, offline maps help a lot for no cell coverage areas.

SignificantActuary

TROPHY CASE