Okay, I have tested, and this is working with Insteon.
https://dl.dropboxusercontent.com/u/241 ... 0v2.10.zipThat being said, v2.10 also has revised hop timings, so please send me feedback on them.
v2.20 or v2.30 will be available within 3-4 days, which should support Zwave network testing.
I am being forced to build out a Zwave network, and all I have right now is a Zwave Energy meter, which I can't reach from my Indigo server. I was hoping the energy meter device would be close enough, but it isn't. It looks like I am going to have get some repeaters to make that work. So if anyone would like to help , I won't argue with Zwave donations...
Changes since v2.00 (6/19/2014):
⁃ v2.10 - Released 6/26/2014
⁃ Using Indigo API V1.16’s Ping command, so we can now test Insteon and Z-Wave (Pending) devices in a cross-platform manner.
⁃ Switched to using the Ping results from Indigo’s API. This should be more accurate and dependable.
⁃ Due to the switch to Indigo’s results, I am switching the timings to Milliseconds, instead of seconds.
⁃ v2.10 REQUIRES Indigo v6.0.13 or higher, due to the dependency on API v1.16.
⁃ v2.10 now uses the WaitUntilIdle Server command, so this should help prevent any stalls from other requests from Indigo.
⁃ v2.04 - Released 6/22/2014
⁃ Suppress the duplicate address warning for fanlinc devices. The duplicate device won’t be counted / pinged, but you won’t receive the warning message for it.
⁃ v2.03 - Released 6/21/2014
⁃ Added warning message regarding duplicate devices with identical addresses
⁃ The plugin will ignore the 2+ device with a duplicate device ID
⁃ v2.02 - Released 6/20/2014
⁃ Fixed a typo in the hop heat map lookup table
⁃ v2.01 - Released 6/20/2014
⁃ Bundled the wrong version for previous release. Re-released as v2.01.
⁃ v2.00 - Released 6/19/2014
⁃ First general release