bigscience

So I think I finally figured out the hardware side of things. I ended up cutting a phone wire and putting the red and green wires into the ground and sensor inputs on a I/O Linc. Normally, when there is no alarm, the connection in made on these wires but when an alarm is triggered, a relay comes on and flips them on and off. This is all it takes to trigger a signal to the ISY. I wrote a simple program to send a text saying the alarm was triggered. If Control 'IO Sensor' is switched Off Then Send Notification to 'BradCell' content 'Alarm' Wait 15 seconds Send Notification to 'BradCell' content 'Alarm' Else - No Actions - (To add one, press 'Action') It works and sends me 2 texts so hopefully I don't miss the first one. I'm not sure if there is a more elegant way to wait for a bit to make sure it wasn't an accidental set off or to keep sending them if the alarm is still on. Overall I'm happy that I can keep my current alarm for now and can cancel my land line. Thanks ISY!

The other thing I was thinking about doing was since I woun't be using the phone lines in it (it has a line in and line out), was to connect the two of them with a IO Link between them. My thought is that when it tries to dial, it would connect between the line in and put it's dialing out. This would signal the IO link that something happened? It's also a little easier hack since it would just be a phone line splice. Thanks for the LED idea, I hadn't thought of that. I'll post back if I get anything figured out.

I have a Skylink Wireless alarm system with a dialer to give me a call when the alarm goes off. Everything works fine but I'd like to get rid of the land line and just use ISY to send me a text when the alarm goes off in stead. Has anyone ever done any integration with one of these systems? http://www.amazon.com/Skylink-SC-1000-C ... B0002YPFBS I looked inside the dialer and there are a set of contacts that look they are for hardwiring the dialer to an IO Link to trigger the dialer but I'm looking to go the other way. http://www.smarthome.com/73210/I-O-Linc ... Kit/p.aspx Any thoughts?

So I updated Java with the same outcome. Then I added my add ISY address as an exclusion to Avast and now it works. Hopefully this can help someone else out down the road. I'm still not sure why this just became an issue.

When I turn on/off lights from the admin console, there is no status. Current State is blank and the On level is 0%, the Ramp Rate is 9.0 Min. I Disabled the Avast Web Shield and then reloaded the Console and it then worked as expected. What I'm not getting is how this could happen? I'm wondering if it has to do with a Java update that I haven't done yet (Avast blocks parts of it in ISY). I'd rather not update that and then also have to update the ISY to a Beta. I'll see if there is a way to 'trust' the ISY in Avast. Any other thoughts? Thanks for the point in the right direction too.

I went into the Admin console yesterday and wanted to change a few lights settings but nothing was being written. Then I noticed the button that toggles on/off the writing of changes is not there anymore. I tried to right click on the switch and use 'Write Updates to Device' option but this didn't write either. I tried to restart the ISY 994i and I get the same thing. Any thoughts? I'm running v.4.0.5 on an 994i Pro with 1758MB Free and the PLM shows as connected. I can turn lights on/off from the console too. Thanks for the help.

Rats. I guess I need to find a spot to put the smoke bridge where SWMBO can't unplug it and forget to plug it back in. Thanks for the info.

So is there anyway to tell if it's still plugged in? How does the 'is responding' work?

I do have a 994 Pro version 4.0.5. For the smoke bridge, I'm showing nodes smoke, CO, Clear, Low Bat, Malfunction, Test and Unknown Message. I'm not sure what Clear and Unknown Message are for. Is one supposed to be the heartbeat like on a leak sensor? Thanks for the help.

I just got and hooked up a smoke bridge and a few detectors. I've got all the alerts working via text but am wondering if there is a way to let me know if it get's unplugged (kind of like the heartbeat on the leak sensors). Would a "is responding" once a day work? What exactly does "is responding" do when in a program? Would it ping the smoke bridge and then report back the results?

That's what I thought I could do but after I did a factory reset, the ISY couldn't communicate with it. I thought it broke the link between the ISY and the KPL with the factory reset. I couldn't get it to work without removing and adding the KPL back in. I guess I should have tried a little harder. Thanks for the help, I'm still leaning here. I like what I'm seeing so far though.

For Status, in a program I can choose >Off or Is Not Off. I get that 10% is not 'ON' but is >Off. I just don't get why there is an "is not off" when ">off" looks to do the same thing. Am I missing something? Is there a case where you'd use one over the other? Thanks for the help.

Sorry if this is a dumb question but what's the difference between status >Off vs Is Not Off?

I never was able to solve this with just the ISY (restore or anything) so I ended up removing the KPL, doing a factory reset at the unit and then relinking to the ISY. Everything seems to be working great now. I wish there was a way to do the factory reset and then restore from the ISY so I didn't have to recreate all the scenes. If there is and I couldn't figure it out, please let me know in case this ever comes up again.

Did a test scene and got this: Sat 12/14/2013 06:33:32 PM : [GRP-RX ] 02 61 30 13 00 06 Sat 12/14/2013 06:33:32 PM : [iNST-SRX ] 02 50 1D.F4.D3 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:32 PM : [std-Cleanup Ack] 1D.F4.D3-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/14/2013 06:33:32 PM : [iNST-SRX ] 02 50 0D.32.1C 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:32 PM : [std-Cleanup Ack] 0D.32.1C-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/14/2013 06:33:32 PM : [iNST-SRX ] 02 50 22.76.6F 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:32 PM : [std-Cleanup Ack] 22.76.6F-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/14/2013 06:33:33 PM : [iNST-SRX ] 02 50 14.CA.C8 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:33 PM : [std-Cleanup Ack] 14.CA.C8-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/14/2013 06:33:33 PM : [iNST-SRX ] 02 50 1D.D0.82 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:33 PM : [std-Cleanup Ack] 1D.D0.82-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/14/2013 06:33:33 PM : [CLEAN-UP-RPT] 02 58 06 Sat 12/14/2013 06:33:33 PM : [iNST-SRX ] 02 50 13.9F.CE 25.16.EB 61 13 30 LTOFFRR(30) Sat 12/14/2013 06:33:33 PM : [std-Cleanup Ack] 13.9F.CE-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 ----- Home Test Results ----- [succeeded] Kitchen Cans Controller (22 76 6F 1) [succeeded] Stairs (1D D0 82 1) [succeeded] Kitchen Cans (D 32 1C 1) [succeeded] Living Room Cans (13 9F CE 1) [succeeded] Landing (Kitchen) (1D F4 D3 3) [succeeded] Landing (Living Room) (1D F4 D3 2) [succeeded] Landing (Stairs) (1D F4 D3 1) [succeeded] Landing (Home) (1D F4 D3 7) [succeeded] Living Room (Stairs) (14 CA C8 1) ----- Home Test Results ----- Sat 12/14/2013 06:33:40 PM : [iNST-TX-I1 ] 02 62 00 00 30 CF 13 00 Sat 12/14/2013 06:33:40 PM : [iNST-ACK ] 02 62 00.00.30 CF 13 00 06 LTOFFRR(00) Sat 12/14/2013 06:33:40 PM : [ 1D F4 D3 3] ST 0 Sat 12/14/2013 06:33:40 PM : [ D 32 1C 1] ST 0 Sat 12/14/2013 06:33:40 PM : [iNST-TX-I1 ] 02 62 00 00 18 CF 11 00 Sat 12/14/2013 06:33:40 PM : [ 22 76 6F 1] ST 0 Sat 12/14/2013 06:33:40 PM : [iNST-ACK ] 02 62 00.00.18 CF 11 00 06 LTONRR (00) Sat 12/14/2013 06:33:41 PM : [iNST-TX-I1 ] 02 62 00 00 36 CF 13 00 Sat 12/14/2013 06:33:41 PM : [iNST-TX-I1 ] 02 62 00 00 18 CF 11 00 Sat 12/14/2013 06:33:41 PM : [ 1D F4 D3 3] ST 255 Sat 12/14/2013 06:33:41 PM : [iNST-ACK ] 02 62 00.00.36 CF 13 00 06 LTOFFRR(00) Sat 12/14/2013 06:33:41 PM : [iNST-TX-I1 ] 02 62 00 00 21 CF 11 00 Sat 12/14/2013 06:33:41 PM : [iNST-ACK ] 02 62 00.00.18 CF 11 00 06 LTONRR (00) Sat 12/14/2013 06:33:42 PM : [iNST-ACK ] 02 62 00.00.21 CF 11 00 06 LTONRR (00) Sat 12/14/2013 06:33:42 PM : [ D 32 1C 1] ST 255 Sat 12/14/2013 06:33:42 PM : [iNST-TX-I1 ] 02 62 00 00 18 CF 11 00 Sat 12/14/2013 06:33:42 PM : [ 22 76 6F 1] ST 255 Sat 12/14/2013 06:33:42 PM : [iNST-ACK ] 02 62 00.00.18 CF 11 00 06 LTONRR (00) Sat 12/14/2013 06:33:43 PM : [iNST-TX-I1 ] 02 62 00 00 36 CF 13 00 Sat 12/14/2013 06:33:43 PM : [iNST-TX-I1 ] 02 62 00 00 18 CF 11 00 Sat 12/14/2013 06:33:43 PM : [iNST-ACK ] 02 62 00.00.36 CF 13 00 06 LTOFFRR(00) Sat 12/14/2013 06:33:43 PM : [iNST-ACK ] 02 62 00.00.18 CF 11 00 06 LTONRR (00)