Problems with 510 build

[seallred]

I have been playing with some things and have identified what seems like a few problems.

The components I have enabled include: Customer Weather, Geographical Location, MediaBridge, Sun Clock, USBUIRT.

I am testing with the "FlatStyle Music and DM" CCF that is provided.

I have updated Custom Weather to include a couple different cities.

1. After restarting girder on my home automation server and connecting up with NetRemote things work great. Once I shutdown NetRemote and I fire it back up the Lights and Appliances panels don't work for me. None of my Insteon devices show up at all.

2. When I go to the Sun Clock from the home page in Net Remote nothing shows. I have never been able to get this to work.

3. Custom Weather works the first time I launch Net Remote after restarting Girder. But if I shut down NetRemote and then start it back up it is blank.

4. I currently have 2 mediabridge servers setup so I can enable 2 zones on NetRemote. When I choose the "Zones" I see both of them. The problem is when I change zones. The text for Current Zone and Current Host doesn't get updated unless I change panels (i.e. go to Home and then back to Music). I just noticed it will also change when I change panels within the Main Music panel.

5. When on the tree view and you select Zones the zone window is hidden behind the Tree View.

I just tried a few different things to try and isolate the problem that I am seeing when I launch NetRemote for the second time and the only thing that works is the Music panel. I shutdown my PC running NetRemote while leaving Girder running. I wanted to see if NetRemote was causing the problem because maybe it wasn't shutting down cleanly. When I restarted and launched NetRemote I still saw the problems described above. So then I restarted Girder and when I connected with NetRemote everything worked fine so it seems to be Girder. Am I just seeing these problems or are others?

By the way, I love this technology, great job!

Thanks,

[Rob H]

Is this over a WiFi connection?

It's possible that you're not leaving it long enough before starting up NR again, Girder may not realise that the connection has been closed.

Although NR should be asking Girder for a DM update regardless.

The sunclock problem is a known one.

[seallred]

No it is over a hard wired direct connection. I actually see the NR connection open and close in the log display. Here is the output I get in the Girder Log Display:

Time Date Source Details Payloads
18:29:49:190 1/19/2007 NetRemote Exiting feedback thread for 192.168.0.102
18:29:49:190 1/19/2007 NetRemote Closing client for 192.168.0.102
18:29:49:190 1/19/2007 NetRemote Unregistering NetRemote client 192.168.0.102:2152
18:29:49:190 1/19/2007 NetRemote Connection closing 192.168.0.102:2152
18:29:49:190 1/19/2007 Communication Server Close Connection 192.168.0.102 2152
18:29:49:190 1/19/2007 Communication Server Close Connection
18:29:41:331 1/19/2007 TaskSwitch girder.exe
18:29:37:128 1/19/2007 NetRemote Synchronising client 192.168.0.102 {2d598515-4828-431a-9a1c-03dfd4d9120c}
18:29:37:128 1/19/2007 NetRemote Connected
18:29:37:065 1/19/2007 NetRemote Starting feedback thread for 192.168.0.102
18:29:36:956 1/19/2007 NetRemote Registering NR client
18:29:36:956 1/19/2007 NetRemote Adding client 192.168.0.102
18:29:36:940 1/19/2007 Communication Server New Client Connection 192.168.0.102 2152
18:29:36:940 1/19/2007 NetRemote Connection from 192.168.0.102:2152
18:29:36:940 1/19/2007 Communication Server Connection Authenticated 192.168.0.102 NetRemote

[Rob H]

Are NR and Girder running on the same PC or different ones?

[seallred]

Different. Girder is running on a server down in my basement and NR is running on my laptop.

[seallred]

I just ran a test with a wireless connection and I got the same exact results that I described in my original post.

[seallred]

Bump!! I am still having the following problems with Girder 5 Build 516.

I am testing with the "FlatStyle Music and DM" CCF that is provided.

1. After restarting girder on my home automation server and connecting up with NetRemote things work great. Once I shutdown NetRemote and I fire it back up the Lights and Appliances panels don't work for me. None of my Insteon devices show up at all.

2. When I go to the Sun Clock from the home page in Net Remote nothing shows. I have never been able to get this to work.

3. Custom Weather works the first time I launch Net Remote after restarting Girder. But if I shut down NetRemote and then start it back up it is blank.

Anyone else seeing this behavior?

Girder 5 Build 516 / Media Bridge 2.2.0.78 / NetRemote v2.0.0.92 / Insteon Plugin 1.4.5 / PLC Firmware 2.13

[curtiswren]

I get the same behaviour here. I mentioned it in another post, but have not been able to get it resolved.

[Rob H]

Can you load DebugView from www.sysinternals.com and set the filters to monitor just NetRemote.exe?

Then start NR and Girder in that order and save the output to a file.

Clear the DebugView log and restart NR then save the output to another file.

Upload both files here and I'll see if I can work out what's happening.

[seallred]

I followed your instructions and the output is attached in the zip file. I also attached screen shots of NetRemote after each launch of it. So, debugview1.log goes with netremote1.gif and debugview2.log goes with netremote2.gif.

Also, a little more information for you. I have girder running on my home automation server in the basement and I am running NetRemote from my laptop. Like I have said earlier it happens regardless of wired or wireless connection. I did load NetRemote locally on my home automation server and I didn't experience any of the problems that I mentioned.

Hope this is information is helps the debugging process.

[Rob H]

I can't reproduce this here at all I'm afraid.

Open the Interactive Lua scripting console in Girder and restart NR. Do you see messages along the lines of


Registering NR client from 192.168.1.105:1425
LOG: Device Manager : 4 - Connection manager: Got a DM.Query from NetRemote client at 192.168.1.105


If not, then we have a problem with either Girder or NR not recognising that the connection has dropped and been restarted. So, with NR running try resetting Girder and go to File|Settings and select the NetRemote page from the Automation section on the left. You should see the NR instances that are connected in the list.

Close NR - the entry for that connection should change to show "(not connected)"

Start NR again and the "(not connected)" should disappear.

[rpalmer68]

I've also had this issue in the past, the only way Girder would update NR was to reset (F11) girder after I'd restarted NR.
But haven't had it for a while as I'm sure we found a fix for it.


Rob, wasn't there some issue with girder instance numbers in NR, and I had to delete my girder instance and let NR auto discover Girder again?

The other thing that caused me problems was when I used as IP address instead of the computer name for the plugin instance.

seallred, maybe try this, delete the girder plugin instance, then enable Auto Discovery so NR finds girder again, then disable Auto discovery once it's found.

And make sure you have the hostname not the IP address set for the girder instance.


May not help at all, but I know how frustration this issue is so it's worth trying.

Richard

[Rob H]

That is a possibility if the real Girder plugin instance is actually numbered -1 then that might cause this symptom. Good thinking.

[seallred]

That fixed it. Thanks for the help I appreciate it. I had changed from using computer name to ip address for some other reason and hadn't changed back. Anyway, everything is working now. Thanks again.

[curtiswren]

I've made some progress. I've got this working with 2.0.0.92 on Vista and my Dell PPC. I still can't get it to work on my iPAQ though. It is using the same version of NR and the same CCF/LUA file. The Dell PPC is an X51v with windows mobile 5. The iPAQ is a h4100 with windows mobile 2003. All the settings seem to be the same between the two. Both have -2001 as the girder instance id and use host name. When I start up using the Dell, I get the message that says "Got a DM.Query from NetRemote client". When I run with the iPAQ, I don't get this message. Any suggestions on where to go from here?

Thanks,

Curt

[Rob H]

Curtis,

Do you see the iPaq client registering with Girder at all?

[curtiswren]

It seems like it keeps repeating the connect message. Everything else seems to work though. Here's the girder logs:

Interactive Lua Console


Registering NR client from 192.168.1.103:1095
Registering NR client from 192.168.1.103:1096
Registering NR client from 192.168.1.103:1097
Registering NR client from 192.168.1.103:1098


Log Display


Time Date Source Details Payloads
20:11:54:062 4/1/2007 Communication Server DM.DeviceUpdateDone 34700 192.168.1.101 281
20:11:51:218 4/1/2007 Communication Server DM.DeviceUpdateDone 36132 192.168.1.103 279
20:11:50:875 4/1/2007 NetRemote Synchronising client 192.168.1.105 {ffffc5e7-ed5b-4fff-8cc5-ffff9ffdffff}
20:11:50:875 4/1/2007 NetRemote Connected
20:11:47:890 4/1/2007 NetRemote Starting feedback thread for 192.168.1.105
20:11:47:875 4/1/2007 NetRemote Registering NR client
20:11:47:875 4/1/2007 NetRemote Adding client 192.168.1.105
20:11:47:875 4/1/2007 NetRemote Connection from 192.168.1.105:1041
20:11:47:875 4/1/2007 Communication Server New Client Connection 192.168.1.105 1041
20:11:47:875 4/1/2007 Communication Server Connection Authenticated 192.168.1.105 NetRemote
20:11:47:843 4/1/2007 NetRemote Exiting feedback thread for 192.168.1.105
20:11:47:843 4/1/2007 NetRemote Closing client for 192.168.1.105
20:11:47:843 4/1/2007 NetRemote Unregistering NetRemote client 192.168.1.105:1040
20:11:47:843 4/1/2007 NetRemote Connection closing 192.168.1.105:1040
20:11:47:843 4/1/2007 Communication Server Close Connection 192.168.1.105 1040
20:11:47:843 4/1/2007 Communication Server Close Connection
20:11:37:000 4/1/2007 Communication Server DM.DeviceUpdateDone 35332 192.168.1.102 273
20:10:43:593 4/1/2007 Communication Server DM.DeviceUpdateDone 35332 192.168.1.102 269
20:10:12:218 4/1/2007 Communication Server DM.DeviceUpdateDone 24060 192.168.1.105 276
20:09:57:296 4/1/2007 Communication Server DM.DeviceUpdateDone 34700 192.168.1.101 277
20:09:54:421 4/1/2007 Communication Server DM.DeviceUpdateDone 36132 192.168.1.103 275
20:09:54:000 4/1/2007 NetRemote Synchronising client 192.168.1.103 {ffffbb15-d942-4fff-ba9e-ffffe59fffff}
20:09:54:000 4/1/2007 NetRemote Connected
20:09:51:062 4/1/2007 NetRemote Starting feedback thread for 192.168.1.103
20:09:51:062 4/1/2007 NetRemote Registering NR client
20:09:51:062 4/1/2007 NetRemote Adding client 192.168.1.103
20:09:51:062 4/1/2007 NetRemote Connection from 192.168.1.103:1098
20:09:51:046 4/1/2007 Communication Server New Client Connection 192.168.1.103 1098
20:09:51:046 4/1/2007 Communication Server Connection Authenticated 192.168.1.103 NetRemote
20:09:51:046 4/1/2007 NetRemote Exiting feedback thread for 192.168.1.103
20:09:51:046 4/1/2007 NetRemote Closing client for 192.168.1.103
20:09:51:046 4/1/2007 NetRemote Unregistering NetRemote client 192.168.1.103:1097
20:09:51:046 4/1/2007 NetRemote Connection closing 192.168.1.103:1097
20:09:51:046 4/1/2007 Communication Server Close Connection 192.168.1.103 1097
20:09:51:031 4/1/2007 Communication Server Close Connection
20:09:44:765 4/1/2007 Communication Server DM.DeviceUpdateDone 35332 192.168.1.102 266
20:09:18:687 4/1/2007 Communication Server DM.DeviceUpdateDone 24060 192.168.1.105 274
20:08:32:781 4/1/2007 Communication Server DM.DeviceUpdateDone 24060 192.168.1.105 270
20:08:21:000 4/1/2007 Communication Server DM.DeviceUpdateDone 35332 192.168.1.102 262
20:08:18:359 4/1/2007 Communication Server DM.DeviceUpdateDone 35892 192.168.1.103 271
20:08:09:953 4/1/2007 Communication Server DM.DeviceUpdateDone 34700 192.168.1.101 272
20:08:09:578 4/1/2007 NetRemote Synchronising client 192.168.1.103 {ffffbb15-d942-4fff-ba9e-ffffe59fffff}
20:08:09:578 4/1/2007 NetRemote Connected
20:08:07:625 4/1/2007 NetRemote Starting feedback thread for 192.168.1.103
20:08:07:609 4/1/2007 Communication Server New Client Connection 192.168.1.103 1097
20:08:07:609 4/1/2007 NetRemote Registering NR client
20:08:07:609 4/1/2007 NetRemote Adding client 192.168.1.103
20:08:07:609 4/1/2007 NetRemote Connection from 192.168.1.103:1097
20:08:07:609 4/1/2007 Communication Server Connection Authenticated 192.168.1.103 NetRemote
20:08:07:609 4/1/2007 NetRemote Exiting feedback thread for 192.168.1.103
20:08:07:609 4/1/2007 NetRemote Closing client for 192.168.1.103
20:08:07:609 4/1/2007 NetRemote Unregistering NetRemote client 192.168.1.103:1096
20:08:07:609 4/1/2007 NetRemote Connection closing 192.168.1.103:1096
20:08:07:609 4/1/2007 Communication Server Close Connection 192.168.1.103 1096
20:08:07:593 4/1/2007 Communication Server Close Connection
20:07:58:812 4/1/2007 Communication Server DM.DeviceUpdateDone 24060 192.168.1.105 264
20:07:57:562 4/1/2007 Communication Server DM.DeviceUpdateDone 35332 192.168.1.102 257
20:07:40:187 4/1/2007 Communication Server DM.DeviceUpdateDone 35868 192.168.1.103 267
20:07:36:375 4/1/2007 Communication Server DM.DeviceUpdateDone 34700 192.168.1.101 268
20:07:36:000 4/1/2007 NetRemote Synchronising client 192.168.1.103 {ffffbb15-d942-4fff-ba9e-ffffe59fffff}
20:07:35:984 4/1/2007 NetRemote Connected
20:07:33:984 4/1/2007 NetRemote Starting feedback thread for 192.168.1.103
20:07:33:984 4/1/2007 NetRemote Registering NR client
20:07:33:984 4/1/2007 NetRemote Adding client 192.168.1.103
20:07:33:968 4/1/2007 Communication Server New Client Connection 192.168.1.103 1096
20:07:33:968 4/1/2007 NetRemote Connection from 192.168.1.103:1096
20:07:33:968 4/1/2007 Communication Server Connection Authenticated 192.168.1.103 NetRemote
20:07:33:968 4/1/2007 NetRemote Exiting feedback thread for 192.168.1.103
20:07:33:968 4/1/2007 NetRemote Closing client for 192.168.1.103
20:07:33:968 4/1/2007 NetRemote Unregistering NetRemote client 192.168.1.103:1095
20:07:33:968 4/1/2007 NetRemote Connection closing 192.168.1.103:1095
20:07:33:968 4/1/2007 Communication Server Close Connection 192.168.1.103 1095
20:07:33:968 4/1/2007 Communication Server Close Connection
20:07:19:078 4/1/2007 Communication Server DM.DeviceUpdateDone 34700 192.168.1.101 265
20:07:16:359 4/1/2007 Communication Server DM.DeviceUpdateDone 35816 192.168.1.103 263
20:07:15:953 4/1/2007 NetRemote Synchronising client 192.168.1.103 {ffffbb15-d942-4fff-ba9e-ffffe59fffff}
20:07:15:953 4/1/2007 NetRemote Connected
20:07:12:968 4/1/2007 NetRemote Starting feedback thread for 192.168.1.103
20:07:12:968 4/1/2007 Communication Server New Client Connection 192.168.1.103 1095
20:07:12:968 4/1/2007 NetRemote Registering NR client
20:07:12:968 4/1/2007 NetRemote Adding client 192.168.1.103
20:07:12:968 4/1/2007 NetRemote Connection from 192.168.1.103:1095
20:07:12:968 4/1/2007 Communication Server Connection Authenticated 192.168.1.103 NetRemote
20:07:11:343 4/1/2007 Communication Server Existing Client GIRDER HTPC 192.168.1.104 20005
20:07:11:328 4/1/2007 Communication Server Existing Client MediaBridge HTPC 192.168.1.104 20003
20:07:11:328 4/1/2007 Communication Server: Servers Server (GIRDER): HTPC, @ 192.168.1.104:20005
20:07:11:328 4/1/2007 Communication Server: Servers Server (MediaBridge): HTPC, @ 192.168.1.104:20003
20:07:06:828 4/1/2007 Communication Server DM.DeviceUpdateDone 24060 192.168.1.105 259

[Rob H]

First thing I'd try is to delete the Girder plugin instance on the iPaq and enable autodiscovery temporarily. Let it discover Girder again and then disable autodiscovery. That is unless Ben has any better ideas.

[curtiswren]

I've tried that (several times). I even did a complete uninstall/install.

Ben, any ideas?

[Rob H]

Do you have a NetRemote.log file on your iPaq? Not sure where it is supposed to be located these days, probably in the Program Files\NetRemote (or Program Files\Promixis\NetRemote) folder.

That might provide a clue if we're lucky.

[curtiswren]

Here's my NetRemote_log.txt from my iPAQ. Thanks for looking into this.

Curt



19:35:31.172447543] ScriptEngine] INIT: Loading hotkeys
19:35:31.172447656] ScriptEngine] INIT: Loading drivers
19:35:31.172447658] ScriptEngine] \Program Files\NetRemote\plugins\drv_zoom.dll
19:35:31.172447670] ScriptEngine] \Program Files\NetRemote\plugins\drv_avidutils.dll
19:35:31.172447683] ScriptEngine] \Program Files\NetRemote\plugins\drv_generic.dll
19:35:32.172447711] ScriptEngine] \Program Files\NetRemote\plugins\drv_flash.dll
19:35:32.172447744] ScriptEngine] \Program Files\NetRemote\plugins\drv_girder.dll
19:35:32.172447773] ScriptEngine] \Program Files\NetRemote\plugins\drv_webbrowser.dll
19:35:32.172447806] ScriptEngine] \Program Files\NetRemote\plugins\drv_wol.dll
19:35:32.172447831] ScriptEngine] \Program Files\NetRemote\plugins\drv_ir.dll
19:35:32.172447860] ScriptEngine] \Program Files\NetRemote\plugins\drv_MediaBridge.dll
19:35:32.172447895] ScriptEngine] \Program Files\NetRemote\plugins\drv_nrbasic.dll
19:35:32.172447918] ScriptEngine] \Program Files\NetRemote\plugins\drv_xmltv.dll
19:35:32.172447932] ScriptEngine] INIT: Getting skin filename
19:35:32.172447935] ScriptEngine] INIT: Attempting to load ccf
19:35:32.172447946] ScriptEngine] Creating CCF object
19:35:32.172447954] ScriptEngine] Enabling callbacks
19:35:32.172447955] ScriptEngine] Initializing lua
19:35:33.172449057] ScriptEngine] INIT: CCF Loaded
19:35:33.172449223] ScriptEngine] Response: S.MediaBridge HTPC 20003 from 192.168.1.104:1079

19:35:33.172449226] ScriptEngine] Response: S.GIRDER HTPC 20005 from 192.168.1.104:1130

19:35:34.172450231] ScriptEngine] Creating instance -4000

[Rob H]

Hmm.. can you check in File|Properties|Plugins to find out what plugin the -4000 instance is?

[curtiswren]

-4000 is my xmltv plugin. I tried disabling it and still get the same results.