Why not set up backups for the Proxmox VM and be done with it?

Also makes it easy to add offsite backups via the Proxmox Backup Server in the future.

Always mocking Dr. Daniel Jackson. Poor guy

Additional information regarding Home Assistant:

The sun component (which should be enabled by default) already computes the sun position for you.

Elevation and azimuth are available as standalone sensors sensor.sun_solar_azimuth (might be disabled by default) or as attributes on the sun.sun entity.

I don’t have any experience with it but this might do something along those lines(?):

https://esphome.io/components/binary_sensor/ble_presence.html

Seems like you can just add it to one or more of your existing esphome devices.

I could only find the Model 3 in their statistic.

• Year of registration: Breakdowns per 1000 vehicles
• 2021: 1.0
• 2020: 1.3
• 2019: 4.0

The best value for 2021 is 0.8 by the Audi A4 and A5, whilst the worst is the Toyota RAV4 with 17.6.

Overall they rank the Model 3 with “very low” and “low” rate of failure.

Granted these cars are still pretty young so who knows what that figure will look like in 5 or 10 years.

For context they seem to be specifically referencing the 12V “starter” battery not the HV battery used for the traction drive in EVs with that 44.1% figure. Additionally this figure seems to include all vehicles in the statistic, so some part of that is contributed by ICE vehicles.

Indeed

Out of curiosity I’ve let it rate Low<-Tech Magazine, a website run on an ARM SBC powered exclusively with off-grid solar power, and that only achieves 87% / A.

Link to results

If you have such a system up and running already you could try to modify it before ripping it out and starting from scratch.

Borrowing an idea from the machine learning approach you could additionally take the difference in average outside temperature yesterday and the average forecasted outside temperature today. Then multiply that by a weight (the machine learning approach would find this value for you but a single weight can also be found by hand) and subtract it from the target temperature before the division step discussed previously. Effectively saying “you don’t need to heat as much today since it will be a little warmer”.

I fear that’s about all you can do with this approach without massively overcomplicating things.

This is effectively what a thermostat does.

The problem is that the controller won’t know how well insulated each room is, how cold it is outside (including wind speed), which doors and windows are open and when, what people or devices are doing in each room.

The way thermostats solve this is by creating a closed loop where they react to how the room reacts to their actions.

Depending on how your heaters work you’ll likely need some dynamic component to react to these unforeseen changes unless you can live with the temperature being very unstable.

To get a rough idea of how long the heaters will have to run you can look at each room in for the last n days and see if the heater’s runtime was long enough to (on average) hold your target temperature. Dividing the average temperature with the target temperature will give you an idea whether they were on for too long or too short. (If the heaters have thermostats you’ll likely need to subtract a small amount from that value so that it will settle at the minimum required heating time)

If that value is close to 1.0 you know that on those days the heating time was just about perfect.

Once that is the case you can take the previous days heating time and divide it up over the cheapest hours. The smaller of a value n you choose the more reactive the system will be but it will also get a little more unstable. Depending on your house and climate this system described here might simply be unsuitable for you because it takes too long to react to changes.

There are many other ways to approach this very interesting problem. You could for example try to create a more accurate model incorporating weather and other data with machine learning. That way it could even do rudimentary forecasting.

Are there any implementations of this out there or is this purely theoretical (at this point in time)?

* $400 / yr

According to Scott Manley’s video on the topic the probes would need to arrive at the correct time in order to form what is effectively a huge phased array antenna.

Only then is the combined transmission power of these tiny probes large enough to be received on earth.

It is, kind of. The plug is secured by 6 stops (or tabs) along each side. The positive pressure differential pushes the plug outwards into those stops.

To remove the plug you uninstall 4 bolts which allow the plug to go up and over the stops, after which it can hinge outwards on a hinge found at the bottom of the plug.

Source: https://youtu.be/WhfK9jlZK1o?si=dbUV1i2nNFcNixQh

Adding a Turing award to your profile is certainly one way to flesh it out

Typst

You can use their online web-editor (similar to OverLeaf for LaTeX) or download the open-source engine and run it locally (there are extensions available for many text editors).

Compared to LaTeX I find it much more comfortable to work with. It comes with sane, modern defaults and doesn’t need any plugins just to generate a (localized) bibliography or include links.

Since Typst is very young compared to LaTeX I’m sure that there are numerous docs / workflows that can’t be reproduced at the moment but if you don’t need some special feature I’d recommend giving it a shot.

The uom crate implements this for Rust.

The core functionality is based on generics but there are some macros for defining custom measurement systems.

I can’t talk about the other libraries but the uom crate does the same thing.

The dimensions are encoded as a vector of generics, allowing you to get the correct unit even when dividing a distance by time for example.

It’s quite the clever use of Rusts type system.

The development of Piper is being driven by the Home Assistant Project. That probably makes it one of the larger OSS TTS projects. Hope may not be lost yet ;)

Seeing these little IT gems all over Lemmy always makes me smirk :)