fanstel emailed me back - they said both the WM02C and the BM20C are shipping and on their way.

anchor prototype broke - the 3.3v regulator is fried. this is the 3rd out of 5 of the most recent ESP32-based prototypes have broken because their 3.3v regulators killed themselves. i checked the inputs to the 3.3v regulator on a broken board and a healthy one: their inputs are the same, but the broken one outputs 2.8v, and the working one outputs 3.25v

i got all the broken boards out, and their remarkably consistent in their breakage. one of them only outputs 2.8v, one only outputs 3.0v, and one only outputs 2.5v.

im not entirely sure why this is happening. the anchor worked ~5 days ago, and i left it plugged in so the battery didnt die, and 5 days later it no longer works, even off USB power. i havent done anything to preempt this - the anchor has been inactive and not used for 5 days.

do i need to some sort of overcharge protection? does my AC-to-USB-C power adapter just randomly overvolt my stuff? maybe the 3.3v regulator is the first one to break because its the first thing, besides some diodes, that are in the line of fire of the USB or battery? when i first picked up the anchor today, every slight movement of the anchor caused it to beep for half a second. then it stopped entirely.

todo figure out why this is happening.

at first i thought it's because my latest ESP32 batch had battery pads which were very close together and hard to solder to, but that doesnt make any sense, because that would just kill the battery. plus, my 400mah Adafruit batteries have ICs on the batteries themselves that prevent shorts. i tested the batteries on all the broken units, before i disconnected the battery from the board, the battery measured 0.7v, but after i disconnected the battery from the board, it jumped up to 4.1v. it clearly has some protection, and even if it didnt, that doesnt explain the 3.3v regulator breaking.

note: the latest ESP32 batch did not have the following elements on the node before the 3.3v regulator, which the nRF batch coming in does have before the 3.3v regulator: - BLM15BB121SN1D (https://lcsc.com/product-detail/Ferrite-Beads-And-Chips_muRata_BLM15BB121SN1D_120R-25-at100MHz_C85817.html) ferrite bead - https://www.lcsc.com/datasheet/C2907006.pdf resistor

when i added these, i think it was to get past the FCC, not sure if it will help here.

anyways, im going to get my hot air rework station out, and hopefully install a fixed 3.3v regulator. after that, im going to get some sunrise lock footage.

also, i saw what you said in Progress ("and two consecutive misses is the signal Timeline.md says to treat as the plan failing."). you're right, i should probably do things more in order, but im not sure i agree that that constitutes as a full miss. give me time to get in my rhythm, and im not sure i agree that just because i did things out of order, it means im failing the plan.

later at night

successfully used an old board, took its 3.3v regulator, and put it on the anchor, and its all fixed! good as new

using this, i tried filming sunrise lock footage. first time didnt work, there were still some firmware issues, or it could be that my calibration was wrong. told claude to fix it, it did light work on the firmware, and it worked the second time, i got some great footage of it working. i didnt show the 5 minute snooze feature, because i figured its not necessary and just adds unnecessary complexity, although i did mention it verbally in the script. i got a couple shots of me waking up from it, with it buzzing and flashing red. i then picked up the camera, and showed how if i left the room, it turned off, and even if i tried to go back to sleep, it kept beeping. could be better, but definitely good enough for marketing. i did a couple silent takes, and a couple where i live explain what was happening. showed how unplugging the anchor does nothing to help, showed how taking the watch off just makes the anchor go off too, showed how you cant take the anchor off its post.

this just leaves the following for this week: - edit the audio i got - get some more demos tommorow of the phone dock feature, and other b-roll - once those are done, ill start editing the main video together, which will probably take another day, so day after tommorow - day after day after tomorrow, ill take my finished video, get the prelaunch kickstarter up, and launch soonish?

tell me if im wrong,, but as far as i can tell, im on a decent pace.

also, i went into the settings, and fixed the double commit thing on kit - it should autoconfirm emails now. nothing is lost - i didnt have any emails besides test emails anyways