Probably not exactly what you have in mind, but I'd still recommend The Reality Dysfunction (and the other two books in the Night's Dawn Trilogy) by Peter F Hamilton.
In the 70s we had a cassette tape kids story about a wizard who lived in a mountain and kept all the winds in a box.
The story was about someone who went in and retrieved the winds.
It involved blowing up sections of passageways (the narrator talked of lighting the blue touchpaper), and the wizard woke up and chased the hero.
He had a walking stick so his steps were reproduced including that, and he was calling, "My wind! Somebody's stolen my wind!".
I think it was probably on the front of a magazine or something. I don't know if it's a traditional story or something written for that production but I thought it was brilliant at the time.
I have a wired device sending HTTP POST updates very regularly (often more than one per second) and if I watch those arrive, they appear almost instantaneous. If the sending device used IP (or, more likely, had cached the lookup) I guess that would be fast too.
It's probably marginally faster from the dashboard. This isn't only about the ZigBee delay though - it's really perfectly OK. Reducing latency is as much for the fun of it than anything else. I'm interested in knowing what the fastest possible input method is.
That's a good point; the button does support double push, I might be able to disable that. It's some old unit I picked up for next to nothing, I have some Aqura buttons about to try.
Thanks. That means I need to move all data off the hosts on to, say, a NAS - then the NAS becomes the single point of failure. Can I operate a swarm without doing that but still duplicate everything from host 1 to host 2, so host 2 could take over relatively seamlessly (apart from local DNS and moving port forwarding to nginx on the remaining host)?
Step up in this motherfucker just a-swingin' my hair.