Jimbo.Automates

Thanks, I'm going to change one of mine and recheck.

Sounds like the hidden sensor works different than a TriggerLinc, when I change the mode they only send an on, never an off. Sent from my Nexus 7 using Tapatalk

I want to do this as well, but I also use the door sensor (triggerlinc not the hidden one) to show the status of doors. I have a scene DoorOpen and all the triggerlincs are in the scene which also has a KPL button as a responder so I can see if a left a sliding door is open. I haven't figured out a way to do both without a program. I don't use this a security system, I know an ELK is the right way to do that, but haven't moved to that yet... That's next on the list after I'm done with all my insteon & z-wave installs...

Right click on the program and select copy to clipboard, then paste into a post so we can see what you have.

Yes, thanks for pointing out that last paragraph! Sent from my Nexus 7 using Tapatalk

I'm using this http://www.smarthome.com/i-o-linc-insteon-freezer-failure-sensor-kit.html It doesn't monitor temperature, just notifies me if above 39 degrees. Sent from my Nexus 7 using Tapatalk

Thanks everyone. Will be buying them today

Mrbudin, thanks I meant to ask that as well, and specifically the Android Mobilinc. Sent from my Nexus 7 using Tapatalk

Thanks everyone for responding with your experience. I was thinking about getting these locks and now I definitely will. Amazon has them for $172, with prime shipping which looks like a great price. Sent from my Nexus 7 using Tapatalk

That was meant for the OP eyost, not me

Right click on the program and select "Copy to clipboard" Sent from my Nexus 7 using Tapatalk

I can't give an answer why disabling that program would cause a problem, but everytime I think I want a KPL to flash by toggling a scene on and off in a loop I have issues similar to what you describe and have never been able to figure it out. As to the preference for using a variable or run a program, I usually find I need a variable since I might want to break out of the second program example that oberkc showed. Like if the switch was manually pressed... But that is one of the many reasons I love the ISY, different ways to solve the same thing... Sent from my Nexus 7 using Tapatalk

To answer the last question, yes it does look good and I typically write programs using that state machine style. But I would move turning the light on to the second program, or even make it 3 states where 1=light turned on, and 2=waiting. This makes it easier to add other states and triggers later, like motion detection or a manual light control change. Sent from my Nexus 7 using Tapatalk

Also if you push the button on the MS 7 times quickly they send the current duskdawn status if it's different than the previous status so you don't have to wait the 3.5 minutes. I wish the ISY would automatically remember the last reported status of wireless devices so I don't have to create variables and programs for all of them... Sent from my Nexus 7 using Tapatalk

This should be posted in the third party/mobilinc forum or in MobiLinc's own forum Sent from my Nexus 5 using Tapatalk

OK, makes sense. I guess I was assuming that I would add them so their communication status could be seen. Thanks! Sent from my Nexus 5 using Tapatalk

I am trying to add a new Range Extender 2992-222 device, but I get an error "Unsupported Device:0.29". I tried adding it manually but that fails as well. I did search the forums and didn't see anyone mention trying to actually add this device. I am using the latest 4.2.10 Firmware and UI. Is there anything I can do until it's officially supported? Thanks, Jim

Oberck, if you say yours solve both 1 and 2 from the op, that would make this simpler Sent from my Nexus 5 using Tapatalk

oberck, the difference between this setup and the one on the wiki is detailed in the op. I will try to find time later this week or this weekend to add a second button to one of my doors and test it. Jim Sent from my Nexus 5 using Tapatalk

I totally agree with everything you said. Sent from my Nexus 5 using Tapatalk

You should be able to configure the new routers base ip address to what you had before. Was the ISY configured to use dhcp or a hard address? Sent from my Nexus 7 using Tapatalk

Those are instructions to create a client to talk with the ISY. There may be a way to create a ISY module to accomplish this, but that is a lot of work for a simple fix. I've asked UDI to chime in on this subject... Sent from my Nexus 5 using Tapatalk

We know that using a proxy like you mentioned with Google works, examples using a web server on a nas device were posted. To do it with Google opens a lot of security issues that I don't want to get into. I have requested a change for the ISY firmware, of course it is possible, but it was given low priority by UDI. Sent from my Nexus 5 using Tapatalk

An understanding of your intentions you mentioned above would have been helpful. Both MWareman and myself are seasoned ISY user/programmer types along with others in the posts I mentioned above. It was confirmed by UDI that there didn't seem to be a way to do this without a proxy. The easiest fix for this is for the foscam set_alarm to allow the URL with embedded username/password, or have the ISY REST interface allow passing the username/password as parameters. It would be awesome to have a cleaner interface between foscam and ISY so any help you can provide would be appreciated. Sent from my Nexus 7 using Tapatalk

Sorry if I offended you, it was not meant that way. I only a have a few decades of programming experience so you obviously know more than me. But I do have a few years of ISY experience.. I will leave this discussion now. Sent from my Nexus 7 using Tapatalk