Software remote losing connectivity

[dlmorgan999]

I have a few Samsung Q1 UMPCs that I use for software remotes. I've been using these for several years with no issues. I leave them running 24 hours a day.

A bit ago (it seems like it may have coincided with the latest HB update) I started seeing issues where when I come to use the remote after a period of non-use (like overnight or after coming home from work) the remote is no longer communicating with the HB server. In some cases a button press seems to restore connectivity after a few seconds but in most cases I have to close and re-start the remote.

Has anyone else seen anything like this? I don't necessarily think this is an HB issue. It could be a wireless connectivity issue or something caused by a recent Windows update but it's hard to tell.

-- Dave

[ScottBot]

I have a Samsung Q1 also. I do see the remote disconnect from the server, but it always seems to be an issue where the wireless network connection is lost and won't reconnect. I have to manually disconnect from the network and then reconnect.

You might want to enable tracing on the remote and see if that reveals anything.

[dlmorgan999]

Tracing sounds like a good idea. Where does the trace file get generated? FWIW as I was composing the post this morning my Q1 which I had been using a few minutes earlier stopped working again. In my case though I never have to disconnect from the network and reconnect. All I have to do is close and re-start the software remote.

[ScottBot]

I'm guessing that it somehow loses it's connection and then can't get connected back to the server. I've seen an issue where it actually connects back, but the server closes the connection and the whole cycle starts over again.

The tracing on the remote is pretty simple. Each time you start the remote, it will delete the old trace file and create a new one named TraceLog.txt. You can find the trace file in the root of the 'data' directory specified in the SWRemote configuration dialog.

[dlmorgan999]

I came home tonight to find the log had over 900 lines in it (I had to restart the remote first thing today so this is just from today). Here is a sample of what was in the log (it sounds like what you were referring to - this went on for 800+ lines over the span of about five minutes):

12/16/2008 17:36:37 - Client Wakeup is causing a reconnection.
12/16/2008 17:36:39 - Display is now ON
12/16/2008 17:36:42 - Attempting to connect to the server
12/16/2008 17:36:42 - Client is attempting to connect to the server
12/16/2008 17:36:42 - Logging in to Server
12/16/2008 17:36:42 - Connected to the server
12/16/2008 17:36:42 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:42 - Login Successful.
12/16/2008 17:36:43 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:42 - The Server has Disconnected.
12/16/2008 17:36:43 - Display is now ON
12/16/2008 17:36:46 - Attempting to connect to the server
12/16/2008 17:36:46 - Client is attempting to connect to the server
12/16/2008 17:36:46 - Logging in to Server
12/16/2008 17:36:46 - Connected to the server
12/16/2008 17:36:46 - Login Successful.
12/16/2008 17:36:46 - The Server has Disconnected.
12/16/2008 17:36:48 - Attempting to connect to the server
12/16/2008 17:36:48 - Client is attempting to connect to the server
12/16/2008 17:36:49 - Logging in to Server
12/16/2008 17:36:49 - Connected to the server
12/16/2008 17:36:49 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:49 - Client Wakeup is causing a reconnection.
12/16/2008 17:36:49 - Attempting to connect to the server
12/16/2008 17:36:49 - Client is attempting to connect to the server
12/16/2008 17:36:49 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:49 - connection failed: An operation was attempted on something that is not a socket.
12/16/2008 17:36:49 - Client is attempting to connect to the server
12/16/2008 17:36:49 - Logging in to Server
12/16/2008 17:36:49 - Connected to the server
12/16/2008 17:36:49 - The Server has Disconnected.
12/16/2008 17:36:49 - Login Successful.
12/16/2008 17:36:51 - Attempting to connect to the server
12/16/2008 17:36:51 - Client is attempting to connect to the server
12/16/2008 17:36:52 - Logging in to Server
12/16/2008 17:36:52 - Connected to the server
12/16/2008 17:36:52 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:52 - The Server has Disconnected.
12/16/2008 17:36:52 - Client determined server has disconnected because recv() returned -1
12/16/2008 17:36:54 - Attempting to connect to the server
12/16/2008 17:36:54 - Client is attempting to connect to the server
12/16/2008 17:36:54 - Logging in to Server
12/16/2008 17:36:54 - Connected to the server
12/16/2008 17:36:54 - The Server has Disconnected.
12/16/2008 17:36:54 - Login Successful.

[ScottBot]

This is the same thing I've seen before. Can you also run a server trace for me? From the main menu, select "Settings / Tracing...", then check "Server Socket". This should trace the server side of the SWRemote connection.

Also, if you look at the "Software Remotes" view on the server when this is happening, what is the "State" of the SWRemote?

[dlmorgan999]

Ok - I've turned on socket tracing on the server and I'll let you know if anything interesting shows up. I also thought about looking at the state of the remote so I'll keep an eye on that (although often this is happening when I'm not even home).

I just got home a few minutes ago and the remote wasn't responding. I changed to the home page and that seemed to "wake it up".

I looked in the log and didn't see anything this time although curiously the server shows that the remote "logged in at" a few minutes ago (when I tried to use it). This seems odd because I leave that remote running all the time.

[dlmorgan999]

This morning when I first woke up I did an experiment. I left the Q1 untouched and I logged in to the HB server via my laptop. What I found was that the bedroom remote wasn't even in the Software Remote list. As I was looking at the logs (I still hadn't touched the Q1 yet) it all of a sudden decide to connect and show up. This is most likely the first issue I reported and not the continual reconnect. Here is what I found in the server log:

Code: Select all

"12/18/2008","3:36:39 am","TCP Server","Debug","Software Remote [523] Disconnecting"


"12/18/2008","5:36:02 am","TCP Server","Debug","Accepted client connection from 192.168.1.8.  New connection ID = 525"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote Login:  SoftwareRemoteName=[BR-UMPC], ComputerName=[BR-UMPC], Password=[], Connection ID=[525]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] requesting property value for device [231] property [449]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] requesting property value for device [407] property [769]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] requesting property value for device [231] property [449]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] requesting property value for device [231] property [483]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] subscribed to device [231] property [449]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] subscribed to device [407] property [769]"
"12/18/2008","5:36:02 am","TCP Server","Debug","Software Remote [525] subscribed to device [231] property [449]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [231] property [483]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [258] property [68]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [2] property [48]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [196] property [37]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [2] property [97]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [208] property [443]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] requesting property value for device [240] property [466]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [258] property [68]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [2] property [48]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [196] property [37]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [2] property [97]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [208] property [443]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Software Remote [525] subscribed to device [240] property [466]"
"12/18/2008","5:36:03 am","TCP Server","Debug","Initialization signal received from Software Remote [525]"
"12/18/2008","5:36:20 am","TCP Server","Debug","Ping response received from Software Remote [410]"
"12/18/2008","5:36:20 am","TCP Server","Debug","Ping response received from Software Remote [525]"

This evening I was having more problems with the remote and I decided to PING it from the HB server. I noticed that the PING times were very high for a LAN (varying between around 20 and around 120). I finally decided to close the remote and re-start it. As soon as the remote closed the PING times on the Q1 went back to a consistent 1-2ms.

For whatever it's worth I noticed that both of the other Q1 remotes were showing similar behavior in the server trace log so it doesn't seem like a Q1 hardware issue. Further, each of the three remotes is located on a different floor and is served by a different wireless access point so it doesn't seem like it would be a network connectivity issue either.

I'm not sure what all this means yet but I just wanted to provide you with as much information as possible. For me right now this is mostly just a minor annoyance. If you are getting pretty busy with other projects there's no need to work on this right now. It "feels" to me though like this may have started happening with the new version.


-- Dave