Google seems to have set their nest protect units to need six lithium AA non-rechargeable cells. Which is 1.8v, not 1.5v. You put in completely fresh batteries verified with a multimeter at above 1.5v (1.58v iirc) and they’ll complain about it.
I bought lithium rechargeable and they’re 1.5v. Which seems reasonable. I wish all of ‘em would be one standard.
Feels instead like we have AA-, AA, and AA+.
I agree with all of the above, except I’d add encryption to the data.
That way you are not putting your life in their hands, at least until it doesn’t matter / you want the data released. Encryption keys are super lightweight vs data; taken to an unreasonable extreme, a KB could unlock TBs.
Though you’d probably want something more like a passphrase. Anyway, that basic idea is sound but I dunno about the exact delivery/delay mechanism. Gun to my head and I have seconds to decide… scheduled send from a major cloud email provider, pay way in advance, and an increasing flood of calendar events/reminders up to the day it sends. The message would include enough information about the encryption used and formats within that any tier 1 helpdesk level IT person could access the data.
Not perfect, but a good enough balance of simple and robust to start with.