nodejs-poolController VS puppeteer-cluster

It is a bit of work, but maybe https://github.com/tagyoureit/nodejs-poolController

Pool is currently using Pentair EasyTouch, so it’s already controlled/automated in a rudimentary way. I could easy add open source e.g. nodejs-poolController. Then the question would become, how do I continuously or recurringly look ahead at the next 4 days of upcoming weather and perform the necessary calculations, in order to turn my heat pump on and off optimally?

lol. A random stranger on the internet doesn't believe me. What are the chances. Check this shit out ya salty bastard. I know you'll just talk shit anyways since that's what shit talkers do, but this is the first iteration of the raspi project I'm most proud of... it replaces my pool automation system. I saved $2,500k my building my own system and I can even control it with my phone which I think was an extra $500 from Pentair's solution. I used an open source project to communicate with my Pentair equipment. This was before I added two more circuits to control the lighting and waterfall. I learned so much with this project. Took me about two months to do it all. I'll show you a pic of the latest version later since your tears are so tasty to me right now.

Only familiar with Pentair, but this works for me https://github.com/tagyoureit/nodejs-poolController You can do stuff with mqtt but I'm just using the rest API. I have it tied into home assistant, and thus my Google home. We can change the light color with our voice etc. Each evening I have a random light effect turn on, and it turns off when we go to bed. I monitor salt levels with it. Have pool temperature in an IPhone watchface. You should be able to pull off what you want but you'll need to dive in, no pun intended.

I used this to control my Pentair equipment, then used it's API to create entities in home assistant. Might not fit your needs but may help someone else interested in this topic.

If urlsToScrape happens to be large enough, the memory and processor load from spawning dozens or hundreds of pages can bring a system down quickly. Consider puppeteer-cluster.

You could set up a service with something like playwright, puppeteer puppeteer-cluster, browserless, to access the service internally and serve screenshots of it to the outside user. You'd have to set up probably some kind of web service with the appropriate routes.

To make Unlighthouse fast, we combined this lighthouse binary with the package puppeteer-cluster, which allows for multi-threaded lighthouse scans.

https://github.com/thomasdondorf/puppeteer-cluster is doing queue-like mechanism but it is not using redis.

I've used this library: Puppeteer cluster