I agree. I think some of us would rather deal with small, incremental problems than address the big, high-level roadmap. High-level things are much more uncertain than isolated things that can be unit-tested. This can create feelings of inconvenience and unease.
It looks like using Chocolatey [1] saved me from this attack vector because maintainers hardcode SHA256 checksums (and choco doesn't use WinGuP at all).
Interestingly, there are about 100 events of this severity (G4) per cycle, and a single cycle lasts 11 years. This means there are about nine G4 events on average per year.
Note, however, that the solar cycle [0] is so named due to its minimum and maximum: the most severe events will be clustered around the maximum, rather than spread out over the whole cycle (as your comment suggested) - so the "nine G4 events on average per year" is mathematically true but not so helpful.
San Francisco looks nice, but there seems to be a problem with the projection in some of the sample images. It looks as if it isn't UTM but a global sphere projection, which isn't suitable for local renders. It's suspicious that the word 'projection' isn't mentioned in the Readme.
It looks like the final images have some kind of vignetting to make the corners and outter edges fade away. Probably grabbing OSM tiles and doing some image processing.
Yes! However, we are not allowed in Germany to use more than >800W on a Battery with a Schuko Plug, without a certified electrician. Everything is regulated! :D
I have been waiting for the electrician to hardwire the battery for about six months. He said he would stop by next week. Once he has done that, I will increase the maximum charge/discharge power to 1500 W (conservative, I know, but I think I don't need more to fully charge/discharge the battery on regular days).
I don't think this is a Schuko limitation... 800W is a limit that you can send back to the grid without having a properly registered PV plant with a normal inverter. Your meter might disconnect you if you try to send more.
He has 30 kW solar so the registration with the grid operator already happened.
This isn't a grid limitation but a rule about safe home installations. The limits are low for things the general public gets to plug in on their own. Those simple limits don't apply to the same battery installed by a professional. Professionals would instead follow a more complex set of rules and make some calculations, allowing for much higher currents if done in the right way.
What you say is correct. Except: As the AC battery was installed four years after the PV system, I did have to register it separately with the grid operator, which included creating a new entry in the Martstammdatenregister. In other words, registering the PV system and the battery were two completely separate processes for me.
I found out I can automate my 5,12kWh house battery through local-only RS485 connection, and directly setting registers using ModbusTCP from Home Assistant. I then drafted an automation with hysteresis and damping that tries to aim for Net-Zero export/import (pv surplus/grid). It appears to work!
What brand/make of battery is that? I'm tentatively interested in home battery storage, but definitely not interested in shit that requires an app, an internet connection, and shitty saas spyware...
MARSTEK VENUS E 5.12kWh. Got it in August 25 for 1050,00 EUR. It is awesome how open it is designed, I was able to activate and automate it without adding it to my local network (wifi) or using the Marstek App even once. I wrote a blog post here [1].
Thanks for the kudos. Just note, I will add an update tomorrow - I optimized the automatic, it is now working pretty well. Before it was "overshooting" and the battery fed into the grid, or went into standby too often, just to start discharging again.
I would never use what is proposed by OP. But, in any case, Linux on ZFS that is automatically snapshotted every minute might be (part of) a solution to this dilemma.
[1]: https://github.com/crabby-rathbun/mjrathbun-website/blob/83b...
reply