Thanks for the post.
For now the answer will be "No" because 6 hours is the maximum timeout setting and it can neither be disabled. Actually, session timeout gives application an ability to clean up the database and unblock resources.
But, we will surely pass on this feature request to our respective product team.
+1 for this, we also have a large monitoring board and would appreciate the ability to keep a particular user account logged in 24/7. No problem with temporary blocking of the user to perform overnight maintenance tasks within the software as long as the client app can automatically reconnect.
In the OMEssentials database (install the SQL SSMS tool from Microsoft if needed), change the Session Timeout value in the GenericSetting table, Row ID 6 (Session Timeout), set the DataAsInt32 column to 999999999.
To view: xSELECT * FROM GenericSetting WHERE ID=6
To update: xUPDATE GenericSetting SET DataAsInt32=999999999 WHERE ID=6
"x" added to bypass forum oddity. Remove the x to run the SQL commands.