GC100 Tri-Port Connector

[Fryswatter]

Does anyone know or have had any experience with the iFlex using a Tri-Port connector? I'm trying to get communication established with the IR Flex Blaster cable on port 3 of the Tri-Port connector. The IR Flex Blaster cable was the only cable hooked up to the iFlex module to begin with when I installed and configured the GC100 plug-in. However, after removing the IR Flex Blaster cable and installing a Tri-Port Connector to the single port of the iFlex module, I am forced by Global Cache to use port 3 of the Tri-Port Connector and now the GC100 plug-in won't recognize that the blaster cable is attached. I have configured the iFlex to use the Tri-Port with the blaster cable and tested it with multiple API protocol calls and it works just fine. There must be a part of the code in the plug-in to change in order for the plug-in to start addressing "SendProntoCode" to the correct port of the module!

Shouldn't the GC100 parent device create 3 IR port devices to be able to use in scenes?

[a-lurker]

First I'm unsure if this plugin will work with the "Flex" eg

    https://www.globalcache.com/products/flex/

I have used it successfully with this model:

    https://www.globalcache.com/products/itach/ip2irspecs/

Having said that I "imagine" they may be compatible.

You are correct in saying there should be three child devices showing in the UI but sometime back, for reasons unknown, the plugin was changed so that they became hidden. If the plugin is working for you, you may see them listed amongst all this stuff.

<VERA_IP_ADDRESS>/port_3480/data_request?id=user_data&output_format=xml

with the flag like so:  Hidden="0"

Regardless of the above I rehashed the plugin recently, so you could try uploading these files and restart and see what happens:

    http://forum.micasaverde.com/index.php/topic,37268.msg320919.html#msg320919

Once again noting this may not work with the iFlex. Other than than - not sure what your next step would be.

[Fryswatter]

@a-lurker I'll read through the posts to the link you provided. I've had it working for years with just a single blaster cable attached to the iFlex module without a Tri-Port cable. And I do remember when they decided to by default hide the children..lmao. I called them up at support and they explained a few days after they did that. The plugin and devices continued to work without any issues however my uploaded device files ceased to work anymore. That's when I discovered that in the advanced section of the UI, you could select the child device for the IRport and all was well. Just can't figure out why, and I did a fresh plugin install, the addition child devices are not detected when attaching the tri-port cable.

[a-lurker]

Well the change of cable seems to be the issue somehow. However if you want to try to updating the plugin you could follow these steps.
Use the UI to back up the existing plugin files first - always a good move, as plugins seem to come and go:

D_GC100.json
D_GC100.xml
I_GC100.xml

You should be able to "unhide" the existing three children (if they exist) with:

Code: [Select]

luup.attr_set("invisible", "0" ,<deviceID_IR_1>)
luup.attr_set("invisible", "0" ,<deviceID_IR_2>)
luup.attr_set("invisible", "0" ,<deviceID_IR_3>)

return true
in the Lua test window in the UI, where you have inserted the id of the three children above. If they don't exist that would seem to be an issue.

Turn off automatic updates for the GC100 plugin in the UI.

Then overwrite files with the four files from here - noting there is one extra file (L_GC100.lua) You can upload them using the UI upload. Make sure to uncheck the "Restart Luup after upload" then recheck it when upload the last file. After the luup engine restart and after a bit refresh your browser then: If the plugin update is successful you will see this variable: "UseGC100Codes" when the variables are listed in the UI.

Regardless it seems you may have some other problem if it all used to work and a cable change caused problems.

The GC100 code I modified works on Vera and openLuup. Good luck; not sure I can help much further.

[Fryswatter]

Well the change of cable seems to be the issue somehow. However if you want to try to updating the plugin you could follow these steps.
Use the UI to back up the existing plugin files first - always a good move, as plugins seem to come and go:

D_GC100.json
D_GC100.xml
I_GC100.xml

You should be able to "unhide" the existing three children (if they exist) with:

Code: [Select]

luup.attr_set("invisible", "0" ,<deviceID_IR_1>)
luup.attr_set("invisible", "0" ,<deviceID_IR_2>)
luup.attr_set("invisible", "0" ,<deviceID_IR_3>)

return true
in the Lua test window in the UI, where you have inserted the id of the three children above. If they don't exist that would seem to be an issue.

Turn off automatic updates for the GC100 plugin in the UI.

Then overwrite files with the four files from here - noting there is one extra file (L_GC100.lua) You can upload them using the UI upload. Make sure to uncheck the "Restart Luup after upload" then recheck it when upload the last file. After the luup engine restart and after a bit refresh your browser then: If the plugin update is successful you will see this variable: "UseGC100Codes" when the variables are listed in the UI.

Regardless it seems you may have some other problem if it all used to work and a cable change caused problems.

The GC100 code I modified works on Vera and openLuup. Good luck; not sure I can help much further.

Uploaded the files, and now there are no children available nor are they hidden.

Edit: I think I might just create some lua functions and use non-blocking function calls where needed. Hate to have to do that since it's not as simple as using a plugin, but it will suffice.