by Jay on Tue Mar 03, 2009 3:31 pm
It's normal to see that occasionally but not hundreds of times.
Connectivity issues with a wireless client?
Overview of this:
Homeseer must be running prior to starting xlobby for the plugin to connect correctly.
The warning “ In event #64 callback for plug-in xSeer, object removed, error: Can not establish a connection to the remote host "_gtcp://aca5a9a5acf846aa99ca0d089d81b47f". Source: Microsoft.VisualBasic” will appear in the Homeseer log if you shutdown xlobby. This is caused because xSeer doesn't tell Homeseer to remove its call back function when it shuts down. When Homeseer next tries to inform the plugin about changes it finds the callback function is missing and then removes the callback. The message is harmless and can be ignored.
If Homeseer shuts down while xSeer is connected and you have a screen open in xlobby that displays homeseer variables, xlobby becomes very slugish. If you change to a screen without variables xlobby response returns to normal. Once Homeseer is restarted, xSeer will reconnect and response returns to normal.