We need some way for something in the system to notice when interfaces aren't working and try to do something about it.
One (simple) example of this would be for the UI to periodically heartbeat against the server over it's usual web socket. If it doesn't hear back, refresh the page.
Another example would be for the server to ping the client via that same websocket, but then we have a system that watches the logs and, if we don't hear back from a client after a given timeout, email the list, or restart the rpi, or something else.
Anyone who solves a part of this problem in a clean way is welcome to a bounty payment.
We need some way for something in the system to notice when interfaces aren't working and try to do something about it.
One (simple) example of this would be for the UI to periodically heartbeat against the server over it's usual web socket. If it doesn't hear back, refresh the page.
Another example would be for the server to ping the client via that same websocket, but then we have a system that watches the logs and, if we don't hear back from a client after a given timeout, email the list, or restart the rpi, or something else.
Anyone who solves a part of this problem in a clean way is welcome to a bounty payment.
All ideas welcome.