I've only tried it with the device listed in the first post but it should work with any of the IP to IR devices that Global Cache sells. The flex is just a smaller version, easier to hide. It should also work with the wireless to IR, as long as they are on the same network, it'll send the code.
Great thing about Amazon is the return policy...make sure you pick a vendor that will take it back, no questions asked (most will). That way if you do have any problems, just send it back.
If you do try it, please let us know that it works and I'll add it to the post.
Is this app working OK for everyone? I used an earlier version for a while and it worked fine, but due to some Zwave issues I had to remove it all while we were testing as support said it was throwing up some errors. My system seems a bit more stable now I've just tried loading it again using the latest versions of driver and apps. I am getting the following errors is the live log and it is not establishing a telnet connection.
dev:11562018-12-06 12:29:13.641 pm errorjava.lang.InterruptedException: null on line 109 (telnetStatus)
dev:11562018-12-06 12:29:13.616 pm errorTelnet connection dropped...
dev:11562018-12-06 12:29:13.615 pm debugtelnetStatus: receive error: Stream is closed dev:11562018-12-06 11:57:14.079 am [error]
dev:11562018-12-06 11:57:14.079 am errorTelnet connection dropped...
dev:11562018-12-06 11:55:48.187 am debuginitialize error: Connection refused (Connection refused)
Yes, I did read that, but I'm trying to connect for the first time since install using the IP2IR device page initialise button. Does that mean I have to reboot the hub after I have installed the device driver?
Sorry, to see there is some problems with the driver. I have a new version in Github now. It doesn't completely solve the issue but I'm working on it. In the meantime, there is a very simple way of getting it working again. Anytime you have to reset you IP2IR device for any reason, just go into the IP2IR Telnet device and press the 'Initialize' button. Everything will be good again.
Driver Update:
V1.0.2 - 12/06/18 - Minor changes and additional error message. If the IP2IR unit is unplugged or loses connection for any reason, simply go into the IP2IR Telnet device and press the 'Initialize' button.
One question about the child set up - is it necessary to enter the iTach IP address again for each child? Doesn't selecting the specific IP2IR device determine the IP address of the device anyway? Or could a child access a different Itach (if you had more than one) from the parent?
Good catch, it's not needed at all in the child apps. It doesn't hurt anything but it also doesn't do anything. It's just a leftover from a much earlier version. I'll remove it and post an update soon. Thanks!
To use the app with two iTach devices, you would just have to make a second IP2IR device. Then choose that device in the child app.
Just for info, I have had some Zwave issues recently and while support were investigating they said I had a lot of Telnet errors on restarts that were causing knock on issues. Once I reinitialised IP2IR things started running again but I ended up removing IP2IR at the advice of support while they were investigating. The errors were not ones that I could see in my user log, but only visible to support, or I would let you know what they were. I don't know if this was just specific to my system but it might be worth checking with @bobbyD for details in case it's a general problem with the driver or app.
@bptworld, there was discussion about apps having issues reinitializimg after reboots in the thread below. Might be worth a read, especially Chuck's advice a couple of posts down.
Well, I would hope that @bobbyD would contact me if there was an issue with my app. I've been running it for months with no issues at all. It is used every single day.
The only issue someone has mentioned is if they unplug the device for any reason, then you would need to go into the device and hit Initialize again. This is documented in the first post.