In other words, "When you play the game of thrones, you win or you die."

I'm not aware of any automagic way to achieve this result. You'll need to use all4hue, which is basically a wrapper app around the Hue API, to set up rules by hand.

Basically, you'll have a set of rules which update a variable based on the time of day. Then use this variable as a condition in every rule that turns on a light, and have another set of rules triggered by changes to this variable when a light is on. Not complicated, just tedious to program as you'll need 4 rules per light(group) for each of these categories.

But the results work with lights that stay on, lights turned on by dimmers, as well as with motion sensors. And most importantly, the entire thing runs on the bridge so no HomeKit needed. Well worth the effort IMO.

If you're not too picky about specs, eBay will give you one of these nodes for around $200, although you might have to supply the NVMe.

So while the added network layer of Tor (or any overlay network really) certainly adds a level of complexity, from the application standpoint it actually simplifies matters for the following reason: Your application doesn't need any longer to think about the topology of the underlying IP network, as this implicit detail dragged in by direct IP connectivity use is abstracted by the overlay network. Instead, your application is able to interface with any peer via (in the case of Tor) an HTTP proxy and a set of opaque base URLs.

IOW, you're going to need one or more additional daemons to make the P2P part go, and Tor is legitimately the simplest thing available today that accomplishes this without ruling out other styles of overlay network from an architectural point of view.

I'd look hard at the logs, it certainly feels suspicious to me, although admittedly I haven't seen any commentator action suggesting anything other than a flagging campaign.