For some people logging out and back in has helped but I've seen multiple beehaw users state that this doesn't work for them.

This seems to be because beehaw is intentionally staying on an old Lemmy version.

Not sure how the Dev wants to handle this since they've got enough work on their hands and this issue should resolve itself once beehaw upgrades.

For now your best bet is to try re-logging and if that doesn't work to roll back to a previous version of Eternity.

This person had the same issue and they've just logged out and in again

Always mocking Dr. Daniel Jackson. Poor guy

Und an dem Punkt könnte man die Routen und Fahrzeiten dieser Fahrzeugverbände zentral steuern, damit sie immer grüne Welle haben.

Dieses Werk könnte man zB ein Stell-Center nennen.

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.

Dr. med. Maurice Cabanis (einer der Experten) ist schon ein bisschen sus

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

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

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 ;)

Nextcloud is just a web service. How he or anyone can access it is not determined by nextcloud but by the routers, firewalls, vpns and potentially reverse proxies that are routing the traffic to nextcloud.

With the proper configuration of all traffic handling services it will not be possible to access anything other than the intended endpoint i.e. nextcloud.

Within nextcloud any user can only access their own files plus anything that is explicitly shared to them.