Why not have Vera do that? Create a scene on the ISY to turn the keypadlinc button on or off and have Vera activate the scene when the status changes.
- Garrett
You won’t need any HTTP commands.
Create an ISY scene that turns the KPL button on and off. Make note of the scene id, it will be something like “XYZ - Manage Scene” in the editor.
Create a scene in vera, trigger is “device is turned on” for the dimmer in question.
Go to the Advanced tab, you can choose the main ISY device, and hit “Add”
Then you can choose “runScene” and enter the ISY scene number for “id”, and “1” for the newTargetValue (1=On).
Create another scene in Vera, except choose “device is turned off” and set the newTargetValue = “0” (0=Off)
Oops… Garrett beat me to it, on a new page, so I didn’t see it.
Sweet, you guys are both awesome! Thank you! 8)
[quote=“PurdueGuy”]You won’t need any HTTP commands.
Create an ISY scene that turns the KPL button on and off. Make note of the scene id, it will be something like “XYZ - Manage Scene” in the editor.
Create a scene in vera, trigger is “device is turned on” for the dimmer in question.
Go to the Advanced tab, you can choose the main ISY device, and hit “Add”
Then you can choose “runScene” and enter the ISY scene number for “id”, and “1” for the newTargetValue (1=On).
Create another scene in Vera, except choose “device is turned off” and set the newTargetValue = “0” (0=Off)
Oops… Garrett beat me to it, on a new page, so I didn’t see it.[/quote]
Except your reply is more detailed! 
- Garrett
PurdueGuy,
Today, after many months of running perfectly, I started having an issue where the Vera UI does not update with ISY/Insteon devices, even though it controls them properly.
It shows Running & Disconnected.
Rebooting both Vera & ISY several times did not fix it.
Forcing your LUUP code to run (which automatically run every 10 minutes) did not fix it.
Tried Update Names, Restart, etc… only after trying all of this and then using the Stop->Start->Initialize buttons it finally Connected
ISY & Vera are both on the same wired gig LAN - definitely not a communication issue.
Have you seen anything like this? Seems odd that even multiple reboots did not fix the issue?
thx
Your LUUP code in an Automation device:
local runningStatus = luup.variable_get("urn:garrettwp-com:serviceId:ISYController1", "DaemonRunning", 190) local connectedStatus = luup.variable_get("urn:garrettwp-com:serviceId:ISYController1", "DaemonConnected", 190)luup.log("ISYCheck: runningStatus = " … runningStatus)
luup.log("ISYCheck: connectedStatus = " … connectedStatus)if (runningStatus ~= “Running”) then
luup.log(“ISYCheck: Daemon is NOT running - restarting”)
return true
endif (connectedStatus ~= “Connected”) then
luup.log(“ISYCheck: Daemon is NOT connected - restarting”)
return true
endluup.log(“ISYCheck: Daemon is connected & running - not restarting”)
return false
Hmm, I haven’t. Unfortunately, I am not clear on the startup code.
Perhaps Garrett will chime in. Some of the Vera LUUP code is still magic to me. 8)
I’ve seen this. I added a scene that uses luup to look for the status as being either stopped or disconnected. If true, it stops, starts and connects the service with a 15 second delay between each. Another scene does the same thing at 2 am regardless of state.
Could be that the ISY daemon script was removed for some reason. The initialization button copied over the script and started it back up.
- Garrett
Should there be some ISY Initialization code under Apps / Develope Apps / LUA Startup ?
… the only thing I have in there is from PLC/PLEG
It happened again yesterday… no matter what I did, buttons I pressed, even rebooting the Vera, it would never ‘connect’ to the ISY. This morning clicked “Stop” then “Start” then “Connect”, on the plugin menu, and it connected.
I have about 16 devices in the ISY and 1 program… that is all. And, the ISY responds fine to commands directly.
Something is causing it to not properly connect, or maybe it is not really starting properly sometimes even though it says it is?
It will usually work fine for several days.
thanks for the help!
It sounds like some kind of network disruption. Is your vera experiencing luup restarts or system reboots? What version of the ISY firmware are you running? My connections are rock solid between the ISY and Vera. Even more so that I have plex not flooding my network causing my Vera to freak out and restart the luup engine.
- Garrett
I don’t run Plex (btw, why does it cause Vera reboots?)
The ISY (fw 4.0.5) & Vera are on the same gig switch (3’ of wire from each other), same subnet.
I’m running 4.2.x and I believe there are network connectivity fixes. I would log into Vera and run a netstat to see what connections are open on Vera. Just because both devices are close together via connection doesn’t mean something on the network could be flooding the Vera unit.
- Garrett
I am trying to install this on a UI7 versioned vera 3.
I have the daemon running but it says no device detected.
I think this is because I have not set the password or username.
However there is no obvious way to do this.
Help (and be gentle this is all new to me, I just moved from Revol which was simple)
I haven’t tested this on UI7, so I can not be of help. UI7 still has some polish to be done and is lacking features that were in UI5. There are a few who are running it on ui7. So hopefully they can chime in to help.
- Garrett
I downgraded to UI5
I noticed all the plugin files were still there, so I recreated the device, but it said device not ready and the variables wouldn’t save.
So I deleted the device re-uploaded the files and restarted the engine, then clicked reload, I changed the variables (as they now showed up, though they places to put them disappeared even in UI5 at one point).
Still funky so I rebooted the box and when it came back up it was running, it has synced stuff in (dimmers and scenes) - it still says disconnected in the tile - is that normal?
Ah so next set of issues.
-
I have one load being controlled directly by a dimmer. I have added another dimmer as responder / controller pair. Only the load dimmer turns off the load, if I turn off the other dimmer in vera nothing happens
-
While the on/off state seems to get read - it isn’t updating when I when I use vera to change state of the dimmer (i.e. on / off buttons don’t flip status. I also find that 1 in 3 or 4 requests gets dropped or delayed.
Any ideas? could this be related to the disconnected status I see?
Thanks to all for the development on this. I have a question about the way an I/O Linc relay is configured. Control of the relay works fine through vera and I can turn it on/ off. I am using the relay side to control my fireplace and would like for the status of the device in vera to reflect whether it is on or off. At present it does not, although I can see the information coming through the log. Is this how it’s intended to work or is it a bug? I can work around regardless.
[quote=“scyto, post:316, topic:177592”]Ah so next set of issues.
- I have one load being controlled directly by a dimmer. I have added another dimmer as responder / controller pair. Only the load dimmer turns off the load, if I turn off the other dimmer in vera nothing happens[/quote]This is normal operation, and discussed in this thread. That’s how Insteon is designed. If you want both to be updated, use a scene.
[quote=“scyto, post:316, topic:177592”]2) While the on/off state seems to get read - it isn’t updating when I when I use vera to change state of the dimmer (i.e. on / off buttons don’t flip status. I also find that 1 in 3 or 4 requests gets dropped or delayed.
Any ideas? could this be related to the disconnected status I see?[/quote]I would focus on getting the “disconnected” state fixed first. Be sure to refresh your browser as well.
[quote=“kandlg, post:317, topic:177592”]Thanks to all for the development on this. I have a question about the way an I/O Linc relay is configured. Control of the relay works fine through vera and I can turn it on/ off. I am using the relay side to control my fireplace and would like for the status of the device in vera to reflect whether it is on or off. At present it does not, although I can see the information coming through the log. Is this how it’s intended to work or is it a bug? I can work around regardless.[/quote]Are you using the latest build, from the first post in this thread? I fixed that a little while ago.
I bet I am on the third version. I installed a while back and I don’t think I updated to the last one because I wasn’t interested in the leak sensors. Thank you for the response. I’ll try the update tonight.