Netremote connects but no actions

[jnickel]

Hi all,

I have a weird problem. I have a brand new Dell Axim running Version 5.

I have HAI and Russound equipment.

When I use NR Designer and create a new button to send a command to turn a light on/off it works fine from NR in Windows...but the same file does nothing in NR PPC.

I have triple checked connectivity - NR PPC can control Winamp through MediaBridge just fine. The Test under the Girder plugin also comes back fine.
I have also confirmed that I am copying over the right file by making visual changes and checking that my visual changes come across as well.

When I look at the logger, I see it connecting fine, but no actions come across.

Now here is the really weird part - I copied portions of the CCF from a file I had made about 6 months ago. If I click on of those original buttons, I DO get actions happening in Girder. Those old buttons don't have the right actions though.

If I make a new button and assign the correct action in NR Designer, it does not work. However, it does work perfectly from NR Windows.

Very very tired and confused.

Jim

[Ben S]

Can you send me the test CCF, Jim?

[jnickel]

Sure...here is the CCF I am using.

The ones that don't work are everything on the Music page and the Living Room Lights on the Lighting page.

Jim

[jnickel]

Any luck? Have you seen the problem or am I just nuts?

Jim

[Ben S]

It looks like many of these actions are hard-coded against a specific plugin instance (namely -2101). If for some reason you don't have that instance created that could be why.

For me, I don't have a -2101 instance so they came up as IR actions. To fix one, I opened it up (it showed as a RC5x IR code) and changed the ID from -2101 to -1. I then saved the CCF and reloaded it and it showed up properly (And fired).

[jnickel]

Ok,

I think I understand, but I am unclear how I could have avoided this while using Netremote Designer. In order to see/view the actions available on Girder, you have to open up the instance to Girder. I then just dragged and dropped the action/macro into the action list.

What should I have done differently so that it would/will work next time?

Jim

[Ben S]

Hi Jim -
I think you're right. The problem is that each instance can have very different GML files, so it assumes you're going to keep the same instances with the same ID, and that you mean to execute it against a -specific- ID versus the current one.

One way to fix it would be to ensure that all copies of NetRemote have the same instances of Girder configured against the same servers.

I do agree that it might be nice to say "this action, but against the current server", though.

[jnickel]

Nope...I don't understand at all.

If (in NR Designer) I go to the page labelled MUSIC and then go to the Power On button for Living Room, then go to the Action Designer tab and double click the action, all I get is a event string that looks like this:

NRD_b118c0dc-de0f-413b-ba45-1eb5c5706e6b

How can I change anything to a -1 instance from a -2101 instance with that?

I don't have an option to do anything to it.

What should I be doing.

Still very confused.

Jim

[jnickel]

I figured out the issue (with some significant help from Ben!):

You need to make sure that the instance number on the Netremote (Windows or PPC) is the same as what you used when you set it up on Netremote Designer.

To do this in Windows NR, you click File, Properties, Plugins tab, then click the Plus sign beside the Girder, and then right-click the Instance and click on Set ID.

For PPC, you go to Tools, Properties, Plugins tab, then click the Plus sign beside the Girder and then press and hold on the Girder instance. Then pick Set ID.

Make them the same number as you used when creating the CCF on NR Designer and you are set!

Jim

[Ben S]

Thanks Jim.

[nurowolf]

Ben

For reference I had this problem too.

It would appear that the Windows versions of NR defaults its instance to -2101, NR Designer uses this when you are designing your CCF.

By contrast, the PPC version always seems to default to -1.

This had me stumpped for ages - but it is an easy fix once you know whats going on.