Not sure if anyone else has noticed or brought this to your attention, but it seems like when you block the button from phoning home it spends a very long time flashing white and attempting to make a connection each time it is pressed, to the point that one of my buttons I activated a couple weeks ago has already drained 50% of its battery after being pressed twice a day. Another one started with 54 or so and is now "dead" (it reports 13% or so but apparently that's low enough that it's triggering the auto-wipe and won't do anything useful anymore) Seems to me that back in the old days before we worried about blocking them from phoning home I'd get several months out of a button before I had to worry about them running dry. I'm not sure if anything can actually be done about this on your end, but bring it up just on the off chance maybe it can, like some kinda signal be sent to get it to stop trying to connect after the initial pulse goes out or something.

Also I did accidentally leave one button unblocked on my network for a little while and noticed it behaved how it used to (4 or so white flashes and then a quick red flash and shut off) without getting bricked or anything, so I'm kinda tempted to just try leaving one unblocked for a little while and see if maybe Amazon stopped bricking them by now and just returns a generic connection error from their side, since it seems like that'd be nicer on the battery. Kind of suspect this might be the case, like why waste their money keeping update servers up for a device they have no intention of supporting anymore? Guess there's not much harm in trying it with the one that's down to 39% or so since it'd probably be dead in another week or two anyway at this rate. Firmware didn't get updated either (to bricking or non-bricking version) after a few presses like that, green light exploit still worked fine after all was done. Anyone have any info on whether it's safe to just let them access the internet at this point?

Maybe blocking via DNS in my router rather than disabling internet access to the dash button's mac address would also trigger the shorter loop, maybe I'll try that later. For now I guess I'll experiment with leaving one button unblocked and maybe report back if the thing actually gets bricked/updated in the near future.