Pixelblaze becomes unresponsive after a handful of broken websocket connections?

Thanks Jeff, I appreciate the advice!

I could maybe rig a relay up to reboot the PB, but due to some context I left out, if it can be avoided at all I would prefer not to. When the PB reboots the LEDs all flash bright white for a couple seconds before the PB script begins executing again. If that happens when the planetarium building is in pitch-dark mode for a show, it would be very bad for the audience.

I guess I’m hoping for a WS api feature that would allow me to either set the timeout length or manually close “all but this one” connections.