I might have to change from a GC100-12 to a iTach. I have quite a few IR devices, and IR commands in scenes. Do I have to recreate everything ? Or do I just change the IP address in my GC100 device to the new IP of the iTach ? And I have 6 IR ports on the GC100, but only 3 on the iTach . So what happens to the IR devices I have created ? Has anybody tried this ?
Change the IP address … it will reconfigure … the 3 IR ports with the lowest device ID will remain … the others should be deleted.
The switches (for the relays) will be deleted.
If you have more that one iTach … just add another device … goto APPS → My Apps → GC100 add another.
Ok that’s what I was hoping for. I think I will move over. I have a lot of connection issues on iRule with the GC100, and iRule support told me GC100 was a legacy device and an upgrade to iTach should solve the issues…
Do a backup first … you can always restore!
When I tested IR with Vera the one thing I did was modify the I/R output names to align with something more descriptive.
Of course the subordinate child I/R devices were created as invisible devices and thus a simple process I used was:
Confirm Device # for Parent IR Device
http://Vera_IP/port_3480/data_request?id=user_data&output_format=xml
In result set search for id_parent="XXX”
E.g. Example of GC100 device I/R output details
<device id=“300” name=“GC100 I/R Port” device_type=“urn:schemas-micasaverde-com:device:IrTransmitter:1” room=“0” id_parent=“294” disabled=“0"device_file=“D_IrTransmitter1.xml” impl_file=”" manufacturer=“” model=“” altid=“6” ip=“” mac=“” time_created=“1348035340” category_num=“10” subcategory_num="1"embedded=“1” invisible=“1” local_udn="uuid: " commProv=“ir”>
Using Luup to run an update from APPS > Develop Apps > Test Luup Code (Lua)
The GC100 has six I/R ports and thus I set all port to ensure their name is more descriptive. E.g.
luup.attr_set(“name”,“GC100 I/R Port1”,300)
luup.attr_set(“name”,“GC100 I/R Port2”,301)
luup.attr_set(“name”,“GC100 I/R Port3”,302)
So on an so on.
Ok renaming the IR ports is a good idea. Do I need to run that only once or do I put it in the edit startup lua to run every time Vera reboots ?