Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ISY994i Support
#31
(01-03-2020, 04:07 PM)Dean Roddey Wrote: It's getting 404 errors on the services page, which doesn't seem reasonable. That means not found, but that's a pre-defined page that's always there. You don't by some chance happen to have two things on the same IP address do you?

Scenes are just something that never got added. As discussed above, it has to know something is a scene and expose it as such, so it would require specific support for scenes to be added. And it may be that our V2 support for scenes hadn't been fully worked out at the time either.

That ISY should be on a reserved IP.  I will check and reboot it just in case and I'll check my network controller as well.

Bummer about Scenes as the V2 doc shows scenes as supported.  I provided the XML for one scene and it looks like the "family" is the same for all scenes.
Reply
#32
Another dumb question. It may be the trigger thing again but I wouldn't think so with it being a dimmer/switch.

Insteon KeyPadLinc. Trying to use the top load button to then turn on a philips hue bulb in a table lamp.

Is Load Change For() --- is that correct or something else should be used? I then select in Field the KPL61 which shows as ISY-PrimeV2.LGHT#Dim_LVR-KPL61

I have logging selected and I get nothing which tells me it's a problem with the filter?
Reply
#33
Just found the "Event Triggers" in System Info for watching the event triggers info... FANTASTIC!!!! Amazing tool!
Reply
#34
(01-02-2020, 09:45 AM)simplextech Wrote:
(01-02-2020, 08:24 AM)xlurkr Wrote: @simplextech

Are you running 5.XX on your ISY?  I'm looking for someone who can verify that it works with the v2 driver.  I've been holding off upgrading from 4.XX since I don't have any Z-Wave, but I just got a Polisy and it requires 5.XX

-Tom

Yes I'm running 5.0.16B.  I typically run the latest on at least one of my ISY's as I'm part of beta and Polyglot dev group.  Yes Polisy and Polyglot (the nodeserver interface) requires minimum 5.x firmware. 

I've had good luck with the 5.x branch so far with only minor hiccups.  The v2 driver kinda works.  I've noticed not all z-wave devices are visible and in my last check I didn't see any of my scenes.  I just built a new VM last night to give CQC a home of it's own so I'll be doing the install and reconfigure today.

I just bit the bullet and installed 5.0.16B.  After a pause and restart of the ISY driver, it seems to be working well.

I'm not making as full use of the ISY through CQC as you apparently are.  I just use it to trigger some Russound actions based on light switch fast on and fast off actions.  But I'm now capable of testing scenes, the z-wave devices I have, and Polisy.  Not sure what I'm going to do with all of this stuff, but I hope that Dean will support at least some nodeserver nodes in the future as an easy way of adding devices to CQC without adding a full new driver for each one.

-Tom
Reply
#35
(01-04-2020, 11:47 AM)xlurkr Wrote:
(01-02-2020, 09:45 AM)simplextech Wrote:
(01-02-2020, 08:24 AM)xlurkr Wrote: @simplextech

Are you running 5.XX on your ISY?  I'm looking for someone who can verify that it works with the v2 driver.  I've been holding off upgrading from 4.XX since I don't have any Z-Wave, but I just got a Polisy and it requires 5.XX

-Tom

Yes I'm running 5.0.16B.  I typically run the latest on at least one of my ISY's as I'm part of beta and Polyglot dev group.  Yes Polisy and Polyglot (the nodeserver interface) requires minimum 5.x firmware. 

I've had good luck with the 5.x branch so far with only minor hiccups.  The v2 driver kinda works.  I've noticed not all z-wave devices are visible and in my last check I didn't see any of my scenes.  I just built a new VM last night to give CQC a home of it's own so I'll be doing the install and reconfigure today.

I just bit the bullet and installed 5.0.16B.  After a pause and restart of the ISY driver, it seems to be working well.

I'm not making as full use of the ISY through CQC as you apparently are.  I just use it to trigger some Russound actions based on light switch fast on and fast off actions.  But I'm now capable of testing scenes, the z-wave devices I have, and Polisy.  Not sure what I'm going to do with all of this stuff, but I hope that Dean will support at least some nodeserver nodes in the future as an easy way of adding devices to CQC without adding a full new driver for each one.

-Tom

Check your error log.  You'll probably find the ISY driver is connecting/disconnecting fairly frequently and generating these:
Code:
2020/01/04 13:02:20  System    -5012    144
2020/01/04 13:02:27  System    -5012    145
2020/01/04 13:02:34  System    -5012    146
2020/01/04 13:08:17  System    -170001    [UDSockets] RSub:28 error:6
2020/01/04 13:08:21  System    -5012    147
2020/01/04 13:08:25  System    -5012    148
2020/01/04 13:08:32  System    -5012    149
2020/01/04 13:09:39  System    -5012    150
2020/01/04 13:15:52  System    -5012    151
2020/01/04 13:16:00  System    -5012    152
2020/01/04 13:16:08  System    -5012    153
2020/01/04 13:19:49  System    -170001    [UDSockets] RSub:31 error:6
2020/01/04 13:19:54  System    -170001    [UDSockets] RSub:31 error:6

I also hope the ISY driver will be improved on.  I'm hoping to try and package a ISY solution with CQC for those wanting a UI for their ISY deployments.  I'll also work with Dean however needed to change the nodeservers I've developed to make them work with CQC or to port them to CQC native drivers which is preferred really.  Basic nodeservers for the ISY are fine but any that generate a lot of network traffic seem to overload the ISY fairly quickly.
Reply
#36
Even on a new pc the CQC ISY v2 driver is constantly disconnecting and throwing out a 404 error trying to post to /services via GetNodeProps.

I've removed all Polyglot nodeservers and z-wave devices from my ISY and the issue continues. I'm going to move my configuration to another ISY that I have and see if this is a ISY hardware issue. If the errors persist then I know it's a driver issue.

I've also contacted UDI to get previous firmware versions from the last prod/stable release up to the current Beta 5.0.16B release. If the problem persists on my other ISY then I'll start from the last stable release and if everything works then I'll step forward until things break and then I'll get details on what changes were made in that release to break the SOAP interface.

I'm really just hoping this is a hardware issue.
Reply
#37
Mystery may be solved. In reviewing the new PC I put CQC on there were two things I didn't do that I should have.

1. IPv6 was still active on the network interface
2. Windows Power Save garbage was still running.

I disabled IPv6 and all power management for the drives, network and usb controllers last night as it was a late night AHA moment. I forgot this was necessary with Windows and... overnight no weird ISY driver disconnects or reloads or anything.
Reply
#38
Nope... false success. I checked the driver metrics and there were actually 161 comm resets over night and as I'm looking and trying things the driver again lost comm and reset.... ERRRR.....
Reply
#39
I've now tested on 2 different ISY994i systems.
Firmware from 5.013D all the way to 5.0.16B

Same errors and problem with the driver constantly losing connection and reconnecting. I've gone up and down my network and there's zero errors or packet lose connection comm errors. There are no firewalls in between or running on the Windows 10 box.

I removed all z-wave devices, removed Polyglot NodeServers.

I'm going to take a 3rd ISY that I have and drop it's FW down to 4.7.3 and see what happens. I question the outcome as it won't have any devices. If it stays connected then the ONLY big changed between 4.x and 5.x was they changed to use HTTP Chunking. Which would explain a lot of the issues the driver is having if it can't handle chunking. Which leaves this as being a driver issue and I've tore apart my system.
Reply
#40
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.
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Broadlink Support? Darrie 1 315 01-20-2022, 04:09 PM
Last Post: Dean Roddey
  Support for MATTER znelbok 0 283 01-10-2022, 03:08 AM
Last Post: znelbok
  any support for TP Link Kasa natively or third party int? b00ter 1 608 03-13-2021, 06:16 PM
Last Post: gReatAutomation
  Additional MQTT Support znelbok 5 1,952 05-14-2020, 03:55 PM
Last Post: Dean Roddey
  Elk Version Support Issue Ron Haley 20 5,400 05-05-2020, 08:38 PM
Last Post: Shaky
  RadioRA2 Visor Control Receiver - Input support gReatAutomation 12 4,559 02-24-2020, 07:38 AM
Last Post: gReatAutomation
  New MQTT support Dean Roddey 65 20,426 02-02-2020, 02:00 PM
Last Post: simplextech
  ISYv2 Driver - IOLinc Support simplextech 7 3,239 02-01-2020, 07:18 PM
Last Post: simplextech
  Z-Wave Device Support simplextech 6 2,843 01-06-2020, 02:24 PM
Last Post: simplextech
  Insteon Hub Support batwater 37 17,112 09-15-2019, 01:38 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)