ISY994i Support

[simplextech]

IPV6 isn't an issue and should be on, not because CQC needs it (though it will use it), but because Microsoft considers it a non-optional thing these days.

Our HTTP stuff does handle chunked transfers. Though it's potentially possible they are doing something that we've never run into. But that doesn't look to be the issue from the logs. It's the ISY returning 404 errors for the services URL.

I can re-enable the IPv6 that's not a problem even though it's not in use.

yes the 404 is coming from the ISY but the RSub error 6 is happening from the remote subscription of CQC and error 6 is the tcp connection is in a TIME_WAIT from disconnect.  

Something is dropping the connection whether it's the plugin or ISY I don't know yet.  However it's with 2 ISY's running 5.x firmware and the 3rd I've tested with 4.7.3 firmware had 1 reconnect during a few hours time.  Of course the ISY with 4.7.3 had no devices and no activity which may have been why it had no problems.  I don't know.  But I can't restore my config to 4.7.3 from 5.x as they're not compatible (I tried).

[simplextech]

Dean, I noticed that Insteon IOLinc devices aren't being pulled in by the Driver either. Here's the XML for the Sensor and Relay for an IOLinc

<node flag="128" nodeDefId="BinaryControl_ADV">
<address>48 8B 99 1</address>
<name>Garage Door 1-Sensor</name>
<parent type="3">21137</parent>
<type>7.0.65.0</type>
<enabled>true</enabled>
<deviceClass>0</deviceClass>
<wattage>0</wattage>
<dcPeriod>0</dcPeriod>
<startDelay>0</startDelay>
<endDelay>0</endDelay>
<pnode>48 8B 99 1</pnode>
<ELK_ID>H15</ELK_ID>
<property id="ST" value="0" formatted="Off" uom="100" />
</node>
<node flag="0" nodeDefId="RelayLampOnly">
<address>48 8B 99 2</address>
<name>Garage Door 1-Relay</name>
<parent type="1">48 8B 99 1</parent>
<type>7.0.65.0</type>
<enabled>true</enabled>
<deviceClass>0</deviceClass>
<wattage>0</wattage>
<dcPeriod>0</dcPeriod>
<startDelay>0</startDelay>
<endDelay>0</endDelay>
<pnode>48 8B 99 1</pnode>
<ELK_ID>H16</ELK_ID>
<property id="ST" value="0" formatted="Off" uom="100" />
</node>

[simplextech]

Any chance to take a look at adding IOLinc support for the ISY Driver?

The current driver also is NOT adding any of my ISY Scenes. The docs and driver should support Scenes but it's not adding any of them. Those are kinda necessary to fully integrate an Insteon environment.

[simplextech]

Deane any chance you've looked into the missing devices and such for the ISY driver?

Missing are:

IOLinc (sensor/relay)
Insteon Remotes (buttons for triggers)
Scenes
Variables (int/state)
Programs (run then)

[Dean Roddey]

I'm deep in fundamental changes to help with Linux platform support.

[simplextech]

I'm deep in fundamental changes to help with Linux platform support.

Fully understand.  Without Scenes that will make some things challenging for testing.  I'll have to work around this for now.

[keepersg]

Fully understand.  Without Scenes that will make some things challenging for testing.  I'll have to work around this for now.
[/quote]

Did you ever find a way to enable Scenes?  That is a significant deficit for this driver since they are major feature of the ISY and really required to take advantage of it's functionality even if you're just using lights.  I'm on 5.0.16C, have a Polisy.

[Dean Roddey]

No, I haven't looked into it yet. I'm currently banging away towards an open source release that I need to get done. There's quite a bit involved.

[kblagron]

Did you ever find a way to enable Scenes?  

I have scenes available with the V1 driver, which is version 2.3, written by Wuench.  I am currently on ISY-994i v4.7.3 firmware.  I was looking to switch to the V2 driver, but the V1 driver having scene and zwave support has made me stay on the V1 version.  It is very stable, very little issues with it.

[keepersg]

Did you ever find a way to enable Scenes?  

I have scenes available with the V1 driver, which is version 2.3, written by Wuench.  I am currently on ISY-994i v4.7.3 firmware.  I was looking to switch to the V2 driver, but the V1 driver having scene and zwave support has made me stay on the V1 version.  It is very stable, very little issues with it.

I did use that driver in my last iteration of CQC but I can't get it to connect now.  Its stuck at 'waiting for comm....'  I had a long pause during which I was revising all of the hardware infrastructure in the house.  I'm now on ISY 5.0.16C and there were many changes to the security protocol, scene and program encoding incorporated into the ISY.  The V2 driver connects right away and works well for the features that have been included.  Rolling back to 4.7.x is not really a reasonable option...it would be easier and cheaper, in terms of time, to buy another ISY and leave that at the current (and I think final) 4.8.  By the way, if you haven't heard, the climate module is now history, and the upgrade to 4.8 is required to handle that.  

I completely understand that Dean's attention and time are occupied at this time and that he can't  focus on this issue.  I'm a hobbyist and I've been doing this for fun for more than... well actually since my buddies and I set up our electronics and rocketry lab when I was in middle school in the 1960's.  I've got plenty of patience, although not much time, but maybe I'll see if my long nascent programming skills can be revived.