Vera and an ISY994i

[PurdueGuy]

That fixed it. I'm using the model 2342-2. I linked it with the ISY using the RemoteLinc 2 option under Link Management. Now it shows up.

I'll let you know if any scene issues come up.

Glad to hear that.   Keep me posted on any other issues!

[93732]

Thank you very much PurdueGuy!  I will have to look into buying some insteon Hidden Door Sensors. 

Secondly, perhaps you can include the variable name change in the first post so that is is more visible?  I was going ask you if you implemented that "revision" in the currently version but luckily stumbled upon your post.

Well, I just commited/pushed changes for the following:

- Fixed UI7 "Cannot detect device" error
- Added Insteon Thermostat support
- Added Hidden Door Sensor (HDS) support

If you can't get the changed from git, I will be updating the first post momentarily.

WARNING: This changes one of the variable names for calling ISY scenes.   See the post here:
http://forum.micasaverde.com/index.php/topic,17309.msg224364.html#msg224364
I don't know what the old code had, so I wanted everyone to be made aware now.

[PurdueGuy]

Thank you very much PurdueGuy!  I will have to look into buying some insteon Hidden Door Sensors. 

Secondly, perhaps you can include the variable name change in the first post so that is is more visible?  I was going ask you if you implemented that "revision" in the currently version but luckily stumbled upon your post.

Happy to help!   And updated!

[boojew]

After following this thread for a while, I finally got this setup and its great! Incredibly responsive!

Two issues that I have run into:
1. This may be superficial as everything appears to be working, but the plugin shows "Running" and "Disconnected"
2. The local status of the devices I am controlling from the Vera is not getting updated. eg from Vera, I turn on a light through the plugub (and it works), but the Vera continues to show the light as off. Same issue if I initiate it from the ISY and/or the light switch. I have tried changing the poll timer to 5s, but that didnt help


Note, I'm on the latest public release of UI7.

Similarly, is there anyway I can trigger ISY programs from my Vera? Or even just scenes? 

EDIT: I came back to this today and #1 seems to have resolved itself. Perhaps just patience? #2 still seems to an issue and I still dont see my programs. Hoping there is a fix for these 2 items

Thanks!

[Aaron]

After following this thread for a while, I finally got this setup and its great! Incredibly responsive!

Two issues that I have run into:
1. This may be superficial as everything appears to be working, but the plugin shows "Running" and "Disconnected"
2. The local status of the devices I am controlling from the Vera is not getting updated. eg from Vera, I turn on a light through the plugub (and it works), but the Vera continues to show the light as off. Same issue if I initiate it from the ISY and/or the light switch. I have tried changing the poll timer to 5s, but that didnt help


Note, I'm on the latest public release of UI7.

Similarly, is there anyway I can trigger ISY programs from my Vera? Or even just scenes? 

EDIT: I came back to this today and #1 seems to have resolved itself. Perhaps just patience? #2 still seems to an issue and I still dont see my programs. Hoping there is a fix for these 2 items

Thanks!

Is everything working for you now?  if not, did you try the latest beta (1.7.2349)?

[boojew]

After following this thread for a while, I finally got this setup and its great! Incredibly responsive!

Two issues that I have run into:
1. This may be superficial as everything appears to be working, but the plugin shows "Running" and "Disconnected"
2. The local status of the devices I am controlling from the Vera is not getting updated. eg from Vera, I turn on a light through the plugub (and it works), but the Vera continues to show the light as off. Same issue if I initiate it from the ISY and/or the light switch. I have tried changing the poll timer to 5s, but that didnt help


Note, I'm on the latest public release of UI7.

Similarly, is there anyway I can trigger ISY programs from my Vera? Or even just scenes? 

EDIT: I came back to this today and #1 seems to have resolved itself. Perhaps just patience? #2 still seems to an issue and I still dont see my programs. Hoping there is a fix for these 2 items

Thanks!

Is everything working for you now?  if not, did you try the latest beta (1.7.2349)?

I am on 1.7.902 now (and pretty sure I was on 1.7.2349 previously) and I'm still seeing frequent disconnects on the  ISY plugin, and hence status not updated, but it does appear to be better. I have added the scene that restarts the daemon, so I am guessing that is what helped. I actually just came back to this thread today for the first time in a while to try and understand the best way to call ISY scenes and/or programs from the Vera. Would be great if someone would add this to post #1.

[boojew]

Anyone having issues where all of sudden names do not propagate from the ISY to the Vera? All I am getting is insteon ID for any new devices I add... and I added a lot cause I just redid my basement

edit: After rebooting my Vera and hitting updates its working again.. SO nevermind..

[DarthVoder]

Well, I just commited/pushed changes for the following:

- Fixed UI7 "Cannot detect device" error
- Added Insteon Thermostat support
- Added Hidden Door Sensor (HDS) support

If you can't get the changed from git, I will be updating the first post momentarily.

WARNING: This changes one of the variable names for calling ISY scenes.   See the post here:
http://forum.micasaverde.com/index.php/topic,17309.msg224364.html#msg224364
I don't know what the old code had, so I wanted everyone to be made aware now.

Oops...
I've been a happy user of this interface for years only to find in the last few days the wheels have fallen off.

Since installing the 2014(?) version I've only been updating Vera firmware as updates have been announced.
This includes updating to 1.7.2931
Of late Universal Devices has been improving their firmware.
I had been on the 5.0.4 firmware but recently updated to 5.0.10 (which has been out since April)

Only recently I noticed that the ISY994 interface app to Vera has been iffy as to updating device status on Vera.

OK.. It's been a while since I've updated the ISY994 interface app for Vera so
I downloaded the latest (6th) revision of the app and uploaded its files.

Now, restarting Lua results in an ISY Lua startup failure every time.

I've tried removing the ISY994 device and deleting all the app files and reinstalling from scratch. Same result.

Today I turned on debug in the ISY994 app and see a likely cause for the failure. If this is resulting from changes
to the Universal Devices firmware I may have been the first to discover a looming problem to be seen
in the future by others.

Attached is a snippet from the Lua log with the error. Any insight as to what's broken and how I might fix it would be appreciated.

<code>
50      07/22/17 16:32:21.355   luup_log:431: ISYController: Initializing plugin... <0x77757520>
50      07/22/17 16:32:21.784   luup_log:431: ISYController: debug: Parsing node 1D 8 5F 1; family = 1; devCat = 2; subCat = 26 <0x77757520>
50      07/22/17 16:32:21.784   luup_log:431: ISYController: debug: Creating Relay for: node 1D 8 5F 1 <0x77757520>
50      07/22/17 16:32:21.785   luup_log:431: ISYController: debug: Parsing node B B5 29 1; family = 1; devCat = 2; subCat = 10 <0x77757520>
50      07/22/17 16:32:21.785   luup_log:431: ISYController: debug: Creating Relay for: node B B5 29 1 <0x77757520>
50      07/22/17 16:32:21.786   luup_log:431: ISYController: debug: Parsing node 3B 89 49 1; family = 1; devCat = 1; subCat = 65 <0x77757520>
50      07/22/17 16:32:21.786   luup_log:431: ISYController: debug: Creating KeypadLinc Dimmer for: node 3B 89 49 1 <0x77757520>
50      07/22/17 16:32:21.787   luup_log:431: ISYController: debug: Parsing node 2D 99 7 1; family = 1; devCat = 16; subCat = 1 <0x77757520>
50      07/22/17 16:32:21.787   luup_log:431: ISYController: debug: Creating Motion Sensor for: node 2D 99 7 1 <0x77757520>
50      07/22/17 16:32:21.788   luup_log:431: ISYController: debug: Parsing node 19 8F 40 1; family = 1; devCat = 7; subCat = 9 <0x77757520>
50      07/22/17 16:32:21.788   luup_log:431: ISYController: debug: Parsing node 1D F4 12 1; family = 1; devCat = 1; subCat = 28 <0x77757520>
50      07/22/17 16:32:21.789   luup_log:431: ISYController: debug: Creating KeypadLinc Dimmer for: node 1D F4 12 1 <0x77757520>
50      07/22/17 16:32:21.790   luup_log:431: ISYController: debug: Parsing node 11 6F 82 1; family = 1; devCat = 2; subCat = 10 <0x77757520>
50      07/22/17 16:32:21.790   luup_log:431: ISYController: debug: Creating Relay for: node 11 6F 82 1 <0x77757520>
01      07/22/17 16:32:21.791   LuaInterface::CallFunction_Startup-1 device 431 function initialize failed [string "--[[..."]:1660: attempt to compare number with nil <0
77757520>
01      07/22/17 16:32:21.791   LuImplementation::StartLua running startup code for 431 I_ISYController1.xml failed <0x77757520>
</code>

[PurdueGuy]

Well, I just commited/pushed changes for the following:

- Fixed UI7 "Cannot detect device" error
- Added Insteon Thermostat support
- Added Hidden Door Sensor (HDS) support

If you can't get the changed from git, I will be updating the first post momentarily.

WARNING: This changes one of the variable names for calling ISY scenes.   See the post here:
http://forum.micasaverde.com/index.php/topic,17309.msg224364.html#msg224364
I don't know what the old code had, so I wanted everyone to be made aware now.

Oops...
I've been a happy user of this interface for years only to find in the last few days the wheels have fallen off.

Since installing the 2014(?) version I've only been updating Vera firmware as updates have been announced.
This includes updating to 1.7.2931
Of late Universal Devices has been improving their firmware.
I had been on the 5.0.4 firmware but recently updated to 5.0.10 (which has been out since April)

Only recently I noticed that the ISY994 interface app to Vera has been iffy as to updating device status on Vera.

OK.. It's been a while since I've updated the ISY994 interface app for Vera so
I downloaded the latest (6th) revision of the app and uploaded its files.

Now, restarting Lua results in an ISY Lua startup failure every time.

I've tried removing the ISY994 device and deleting all the app files and reinstalling from scratch. Same result.

Today I turned on debug in the ISY994 app and see a likely cause for the failure. If this is resulting from changes
to the Universal Devices firmware I may have been the first to discover a looming problem to be seen
in the future by others.

Attached is a snippet from the Lua log with the error. Any insight as to what's broken and how I might fix it would be appreciated.

I have been having the same issue, but haven't had time to track if all down.

I do know part of it has to do with the status field being nil, "", or " " - but I haven't added a long term fix yet.

[DarthVoder]

Another "improvement" on the horizon for the Universal Devices API is "chunked" data. I have this option
turned off on the ISY so as not to complicate things.

I imagine when chunked data becomes the default this will necessitate an update to the ISY Vera app.

Thanks for all your hard work PerdueGuy. Knowing that you've seen this null compare issue I will save my head
and my brick wall and watch this forum for developments.
 

[DarthVoder]

Bump..
Looking forward to the long term (or even an interim) fix for the nil/""/" "issue.

Have been unable to use this isy994 interface plugin for months and really miss the isy994-vera integration.


[/quote]I have been having the same issue, but haven't had time to track if all down.

I do know part of it has to do with the status field being nil, "", or " " - but I haven't added a long term fix yet.
[/quote]

[xlurkr]

This.  Is.  Awesome.  I can't believe it's been around for years and I'm just now learning about it.  Kudos to the authors(s) and everyone who has contributed to it.

I've discovered a bug that I'd like to report.  It's in L_ISYController1.lua, in the function initializeChildren().  The code is missing an elseif statement that checks for the devCat for a thermostat (5).  It jumps straight to the elseif for the subCat.  The result is that, for any devCat higher than 5, it will create a thermostat device, so long as the subCat is one of the ones that is "true" for thermostat.

I discovered it because I have Smoke Bridge that got created as a thermostat.  Its devCat is 16 (higher than thermostat) and the subCat is 10, which is "true" for thermostat.  Later, I added subCat 9 to thermostat, because that's what my Venstar adapter reports it is.  Then, my Synchrolinc (devCat 7 subCat 9) also got created as a thermostat.  That behavior got me looking into the code.

I'm not a programmer, but I hope there's one reading this.  Please make the change to the code in the repository if you are able.

Also, the only thing the Venstar does is report the current temp correctly.  It doesn't report the mode correctly, or let me change it or the setpoints.  If anyone can help me with this, I'd appreciate it.  That level of debugging is probably beyond my capability.

-Tom

[scyto]

Well it seems i haven't been here since Jun 2015 - wow.

I gave up on my vera edge because to be honest it was an unreliable pile of crap, imagine my surprise when i updated the unit today for a laugh and my modified version of the ISU plugin booted perfectly, UI shows the connect state reliably.  I haven't even updated.

I spent 6mo trying to tell vera there system was bugged and they wouldn't have it.... sigh i was right, but hey now it is fixed.

Did anyone code in a way to toggle off the propogation of z-wave devices from the ISY (my vera is a secondary controller to the ISY)
I figured out what items need to be tunred offf but i have zero actual coding skills http://forum.micasaverde.com/index.php/topic,17309.msg227566.html#msg227566

Hmm Vera is looking interesting again, darn just bought homeseer too...

[jec6613]

Well, hopefully somebody sees this ? I picked up a Vera to use as a bridge to my ISY to some fancy Niles controllers, and lo and behold it doesn't work with the latest ISY firmware.

Any updates on debugging the issue?  I don't know enough about the code to even know where to start with it.