Step up in this motherfucker just a-swingin’ my hair.

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.

iBall

Thanks - I’m looking for a pad with no other features other than the USB output, but this does have that outlet.

Nice, thanks! That’s the sort of thing, especially the second one that has USB-C out as well. Neat.

deleted by creator

I’m interested in what other people have found to be the fastest way to deliver events into HA. It’s been a useful thread.

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.

Good point about the MQTT persistence, cheers.

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.

Perceptibly instant is fast enough for me :)

What’s the method you’re using to communicate with HA?

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)?

Thanks. Can I use my existing, single Docker to start a new swarm, or do I have to start from scratch?

Thanks. Could I achieve a simple 2-host solution with Kubernetes though?

So you have Docker itself on a single host (with parts) and all the containers in fault tolerant storage, and the most work you’d have to do in the event of host drive failure is to re-install the OS and Docker itself?

I’ve found Summit the best for me, personally, on Android. I’ve been able to configure it closest to how I used RIF which is what I wanted.

Cool project, thanks!

I want my server to host a desktop that I can use remotely. Not for managing the server itself; like you describe, I use common tools for managing it.

I just need a desktop for a while - sometimes I want to work on a machine that’s not the one I’m physically using. At the moment I simply have an old desktop running Windows; I VPN to home and RDP to to the machine which works very well, but it seems a waste to have a machine running for this purpose only. I could add the machine to the swarm if I could host a desktop in Docker but that’s not really the intent of Docker and doesn’t yield great results.

kasm looks good, thanks - it’s definitely in the area; desktop as a service. I want something I can suspect and go back to, not sure if I can do that on kasm or not but a good tip, I’ll check it out.

This is not to manage or work on the server, I use terminal and web-based UIs for all of that.

This to host a desktop I can use remotely. Sometimes using my local desktop isn’t what I want to do; I might be running a lower power machine, or want to do something I can’t on the machine I’m actually using. Or I might want to use a remote Linux desktop from a Windows machine. Sometimes the other way around.