just post the database and every entity_id for the 27 windows
guys, thank you for all your help and patience. I had to take some time out to “cool off” it really got me pissed, that I could not get that stupid simple stuff into that covid degraded brains of mine. Instead of falling over laughing like every second time he came on, I should have gone right ahead with that bleach and UV stuff, just to be done with it. If only I had known back then…
It will be some time till Ill be back on this project to supply all the things you asked for… I first have to tackle some other stuff:
I had to get an update through my ZoneMinder to fix some stuff, and had to fix some of my config laziness, as we had some guys smearing the neighborhood with Graffiti lately.
But more important, you probably have heard about that ransomware sh*t that’s plaguing the QNAP enviroment since about a week right now, well I got a bunch of em in the family that are clearly EOL and indeed are quite vulnerable now. I never thought my folks exposing their EOL NAS to the WAN. Lucky them, all are actively rsnapshot into my own OMV, so nobody lost any data. Now I need to move a mountain of Data through some very thin DSL. Lots of fun to come. I will clearly need to plan how about getting their data back onto these machines with all that IP switching once a day and DnyDNS taking time to update etc.pp. but even with LAN access, its 14MB/s only, for those who are close by. yawn
Since they are EOL we will upgrade those TS to Bullseye with all the workarounds and patches to fit that Bullseye kernel into the 2 MB DOM partition and stick OMV6 on top of that Debian. Yea I know, 6 is still Beta, but if this will be a problem, I just kind of just walk across the road an knock on Volkers (the OMV guy) door.
I will be on here, as I will integrate all the OMVs into my HA (at least I try it on HA, if I can’t get it to work, I’ll do it in FHEM), so I see if I need to run updates on any of them in future. Probably even trigger it remotely from HA and tracking my family folks to do the updates while they are out, probably not tracking but just sending out a heads up via signal to have them to agree before the update is triggert. Like, requires update, send out signal, owner needs to replay to the message with yes when hes out for more than say an hour or does not need the NAS right now. Along those lines. Some of these machines run VMs in Virtualbox from FatherMande for QTS, my dear lord, ages ago, so it will be an interesting thing to get that done as there is no OMV Extras for virtualbox any more. Probably need to build those ones new too, easier than to mitigate to docker or KVM.
On topic, I found SUN2, and a post from its coder where he explained how to get time per day of sun above xx° elevation, this will be a part of my shading stuff as well. I want shading from elevation of 35° but only if the sun will reach 45° today, something sun doesn’t supply, I thought about storing and using yesterdays values, or more accurately 4 weeks ago values to account for outside temp delay throughout the sun year cycle. But SUN2 provides just the required time the sun will be above say 40° and if this is above 3 hours it sets a persistent input_trigger to true (that one could also switch manually to deactivate shading, two birds in one go), and that will be reset if the time is below 1 minute in autumn. Checked shortly after midnight, one has an option every day to activate or deactivate the shading, inside the shading and also outside the shading period, and shortly after midnight it falls back to automation. I think thats the way I would like it.