It took 5 days for my Heltec Lora v3 #meshtastic router node to use up 6.6Wh of one 18650 cell at 5% air utilization rate (one telemetry message per minute). That brings it to 6.6W / 5days /24h or 0.055W (15mA@3.7V) on average.
Importantly, this node was also powering a #INA219 sensor which was doing the power measurements every minute.
Now I'll be doing a reference measurement without the INA219 and with zero telemetry.
Turns out `tar` can’t incrementally update encrypted archives (makes sense), and it also can’t update an unencrypted archive with just the changes so you’re responsible for ensuring the full chain or snapshot archives which isn’t feasible.
Block-level snapshots are nice, though. The network transfer is more consistent when compared to file level transfers.
Couldn’t get the #beelink EQ12 (n100 CPU) to run from a 30W PoE splitter and a TP-Link TL-SG108PE switch. The cheaper 12V/1.2A splitters would actually turn off while this one stayed on and wouldn’t boot. Didn’t have a monitor to check the console output.
Here is a hot take — instead of investing in AI, @mozilla should be selling hosting services, domains and email hosting, and stay true to the open web stack. Imagine how well you could pair those with Firefox similar to how Chrome does. https://mozilla.social/@mozilla/111896572632380551
@oivaeskola Yes, since HomeAssistant supports running the full “operating system” inside Virtualbox (same as Hass.io) so you can install all the add-ons (basically Docker containers with some meta data) through the built-in tooling. You will need to forward the serial port to Virtualbox machine for the zigbee dongle, but everything else should be possible to configure from the UI.