HouseBot

I assume that the message "The Client is closing and disconnecting from the server" that you see is after the problem time and more likely just the result of you exiting the SW Remote.

Yes, that is exactly right.

Do you see any "The Server has Disconnected" or "Client Wakeup is causing a reconnection" messages in the log?

No, haven't seen any.

Also, is this 100% reproducible (does it happen every night?)? Are there any other commonalities that you have noticed, like does it happen only when the screen is blanked?

It seems to happen every time now, it just varies how long it takes to happen. I have screen blanking turned off for now and haven't recognized any other patterns when it does disconnect.

I could implement some kind of keep-alive logic, but my concern is that it would be a band-aid over whatever the real issue is and my not resove it properly.

At this point I'd be happy with a bandaid. I don't doubt that the root cause is somehow related to my WiFi setup but I've tried every configuration setting and registry hack that I know of and still can't solve anything.



Any TCP/IP experts out there have any other ideas?



Thanks,Alan

acheslow wrote:I have screen blanking turned off for now and haven't recognized any other patterns when it does disconnect.

So is it OK if it never blanks? Or does it still happen?

It still happens even when the screen never blanks.



What seems odd to me is that Netstat is showing an active connection between the touchscreen and Housebot server even when the touchscreen has stopped updating and the HouseBot server shows the touchscreen as 'sleeping'. Its not until several seconds after the SW Remote client disappears completely from the active software remotes screen in HB that the connection disappears from netstat.