paulbates

The discontinued devices and icon switches should not inherently be a problem, they should be upwardly compatible. I wouldn't worry about that. The four click method could get tricky when fast-on (double clicking the switch) is already in the mix. Each person will input their clicks differently. I would explore other, more controlled approaches. You could have him call our text you when he's around and you use a phone app like mobilinc to unlock it when needed. Another possibility: When I used to sprinkle during the day, I gave my lawn guy a remote to turn the sprinkling programs off if they were going when he arrived. But he can be here every week during summer and fall. You could do a similar thing, give him a remotelinc to let himself in and lock on the way out.

Thanks Earlence! Its good to see academia take interest in HA, and security is a great place to start. I worked in IT at UMMC and familiar with UofM's dedication to security and pioneering efforts in the internet we have today. We would certainly like to see what results you are able to share when they are ready. Paul

IE is still under the W10 hood, you find it by typing Internet Explorer in the search box next to the windows icon on the lower left. Its now a "Windows Accessory"! You can pin it to the task bar if you still want it around. To the point made by others, I download the java app one time from the link given on the version release page, and run it directly,

Hi Earlance, I took the survey... UofM is down the road from me, I worked at UMMC in IT in the past. I'm curious, could you tell us a little about the class, and what point of view the survey is looking to explore? Thanks Paul

Ryan What happens when you use the physical on buttons on the lamplinc to turn it on and off? Paul

Insteon communications are stateless, meaning there is nothing keeping an eye on devices outside of normal communications (and the 3am all device query). You'll need to write a program to query the device at a threshold you can live with. I really recommend against query all devices outside of the the 3am checks. Its a lot of traffic load on the insteon network and could have performance and other undesirable side effects. I have found very few cases in almost 10 years of insteon use where this is a problem, and the root cause was needing to address communications problems by adding dual band devices, or filtering certain appliances. The case I do query is my garage door, I have a program do a query after a keypad key in the house is pressed and enough time goes by that the door should be down. Its more of an operational check that the door didn't strike something on the way down and stop. I also check my first alert smoke bridge more often. The point is, I would focus on making sure your insteon network is healthy and address that, and use queries only where there are safety or other specific concerns.

I have the ancestor to this intermatic unit from home depot, its been in service for 14 years. I attribute the few insteon/x10/electronic losses I've had to this unit. The difference between the two units is the amount of coverage insurance you get, $10k for 5 years vs $7.5k for 3 years. I would always have one of these. There are a number of brands, types and models that you should investigate. This, at a minimum, works well. Paul

Hi Calberrt One way is to make these modifications. You'll need to add a state variable (not integer) called dog_out, to keep track of whether the dog is in or out. The 10 second wait and setting the variable will keep the second program from triggering when you first let him out until you close the door after letting him out. Otherwise it will turn the light off right away when you let him out. Use a wait value that is reasonable for how long you would have the door open to let him out. These programs assume that you open the door, let him out and close the door within 10 seconds. If you let him back in within 10 seconds it might get confused. I know my dog is flaky about how long he's out. There are more potential program safeguards, like the first program turning the lights off after 10 minutes as a safeguard. However, if this is a doorwall with a screen, and you keep it open after dark in milder weather, that will get tricky. Backyard lights - Dog out If Program 'Dark Outside' is True And Control 'Sliding Door Open' is switched On Then Set 'Backyard Keypad' On Set 'Landscape Lights' On wait 10 seconds $dog_out = 1 Backyard lights - Dog in If Program 'Dark Outside' is True And Control 'Sliding Door Open' is switched Off And $dog_out = 1 Then Set 'Backyard Keypad' Off Set 'Landscape Lights' Off $dog_out = 0 I would also consider creating a scene for your keypad and and landscape lights, but after you get a solution for your initial requirement worked out Paul

Hi Michel I'm trying to compare my requirements to the portals capabilities. A couple of questions: I access a single ISY remotely. I use port forwarding now, and looking changing that to using my routers VPN server capability, so that I can access other things on my network. I always use a well known, trusted system from the internet to do this. It doesn't sound like the portal does much for these requirements? Does the portal provide any V5 capability in terms of exposing nodes outside of the lan environment, any additional capabilities there? Thanks Paul

So after thinking about it, you might not have to use toggle mode. I've never used non-toggle mode, but maybe sending it an off will turn it off. It's a fairly easy experiment to try. Depends on how if affects the functionality you want, and what the off does. . I've had the scene thing explained to me before, but I don't recall the specifics. The reality is its not that hard to, so I've "accepted the thing I can't change"

If its set for non-toggle on, then then all it can do is send an on. I would try these 2 changes: Set it for toggle mode Adding to what oberkc said, add a statement to turn Living room F off at the end of the program. You'll need to create a scene and add living room F button to it, and switch that off. That will turn off button F, and the program should no longer be true, solving both problems. The button would be off, you press the button The program runs, The program turns the switch back off

So you guys better hurry before Scott Walker builds the wall between the US and Canada

Ironically the X10 PSC01 did/does a better job sensing for me than the IOlinc. I had several sensors connected to PSC01s in my x10 days that made contact just fine. On the iolinc, I got the glow. I'm not handy enough with electronics and eventually gave up.

Hi Ed You can do these things with the right HW and a few simple ISY programs. You also need to use ISY feature under the configuration tab, Emails/Notifications. The manual discusses this section 3.7 - and - set up a gmail account for this, do not use the Default check box Smoke / CO For smoke / co requires 1 or more first alert "One Link" detectors and an Insteon Smoke bridge. You link the detectors together and test per the directions with the First Alert One Link. Then follow the directions to link in the Insteon Smoke bridge. And also add the Insteon Smoke Bridge to you ISY. (It has to be a First Alert that says One Link on the case) The program is simple First Alert CO Detector - If Control 'Security and Fire Alarm / First Alert Smoke Bridge / First Alert Bridge-CO' is switched On Then Send Notification to 'Paul' content 'CO Alarm' Else - No Actions - (To add one, press 'Action') The notification can be one or more email addresses. Mobile providers have an email account that will send to text, check your provider. Follow the same pattern for Smoke Leak sensor Same pattern as above. Buy an insteon leak sensor., link with ISY. Write a similar program that sends specific notification customizations... washer leak, basement leak, etc Garage door Same pattern as above. Setting up the contact sensor and iolinc is a little more involved. You may want to buy the insteon garage kit that comes with everything. You link it to the ISY. You write a program, and it could be more complex. You could have one program each for up and down. Or, you could have a program that waits X minutes when the door is put up. If the door does not go back down in the specified time, send a message Garage door left up If Status 'Garage / Door Sensor' is On Then Wait 30 minutes Send Notification to 'Paul' content 'Garage door left open' Else - No Actions - (To add one, press 'Action') If the door goes down within 30 minutes, the program terminates, and no message is sent. I think mobilic tells you the status of the door, up or down. I'm not sure how to handle the "down only" requirement. Make sure that phones require a password to access? This isn't step by step, but I think gets you started. You may want to do this Set up a gmail account for your house and configure emails and notifications Write test programs to make sure your alerts work Then make each topic a different project and do them individually..e.g Smoke Leak Garage door There are several different learning curves in here and I can tell you from my experience its easy to try to much at once. Paul

It's a .net app. Runs native on windows, runs on mono on a raspberry pi. Search for venlink on the main forum page. Io_guy writes a number of these types of apps and supports them very well. He's already looking a isy v5 versions Paul Sent from my iPhone using Tapatalk

Larry I believe that API is for commercial facility management software / services. Its never been mentioned as a feature in earlier models that I recall. All of the colortouches have the ability to use a local lan API.. thats what you want, and ISY supports it through venlink. Yes you do need a box to run venlink, unless you just want to send commands to it, then the ISY network modules is needed. I have rpis, but I have run it on a windows desktop "family computer" with no problems. io_guy will have to tell you about how degrees C work on it. Paul

Sounds good. Having said that, PM me if you'd like to discuss my proximity to the Detroit river.

Larry, What are you looking for from the T8xxx? As Huddadudda points out, there are additional commercial operations features are added, but no core HVAC value over the T7xxxs. Its the T7900 if you want a humidistat or humidify/dehumidify control, ot the T7850 if you don't. Since they are so close in price, the T7900 (with venlink) gives you another point to read humidity even if you don't control it with the stat. HVAC Parts warehouse continues to stock all of the new series, if you want an T8900. Its $210 here. One of the reviews under T7900 says "free shipping in Canada", you may want to check that out. Paul

I like the Honeywell and know they are a solid HVAC player. I looked hard it last year when shopping for stats. However, I think there are 2 relevant cautions: If they didn't devote resources to create a dedicated local api, they are not supporting that capability. If something doesn't work right, they aren't going to help. Lack of responding to io_guy provides some evidence for this. They can change their web pages and are not managing to solutions that choose to scrape. They could change their pages for their own reasons and that could break the functionality built on it. This is the classic "screen scraping" problem that has flowed over into web scraping. To be candid, I would not build my hvac solution on this, solely because Honeywell is not showing commitment to the local lan requirements / audience. I followed io_guy's lead to the Venstar colortouch series, partially because of the dedicated local lan API and capabilities. They designed their product with local requirements in mind, and have been responsive when it had defects, and recently improved it by adding https: support. Paul

Joe You can set the MS to send "on" only and configure it to a scene so it comes on fast. So the MS turns it on, but not off. Have a program watch for the "on", and other conditions, to decide to wait the right amount of time and then switch off. Its not 100% clear to me, but the program's 'if' could look at if the othe KPL is on already on, or use variables to track its status if other programs are used. Paul

Tim Different devices plugged into the syncholinc have different on / off load behavior. The device needs to be calibrated to how the device you're watching behaves,. Page 5 of the manual describes how to do this. Paul

Michael Factory resetting my MS has become liturgy and is easy enough to try in this case. Pull battery, wait a minute, press set button while connecting battery, wait 10 seconds). and then restore (I don't delete the device from the ISY, just factory reset and restore) Mine exhibits flaky sensing behavior when the battery is dying. It now regular practice for me to factory reset it on battery change and then use the ISY to do a restore device. Paul

Correct, and also "test". The topic of smokebridge limitations was pontificated on the homeseer forum a few years back. One of the users tried pairing a separate smokebridge to each detector to try and know which detector raised the alarm. That part worked, but since there can only be one pairing per detector, the results were equally limiting... meaning that it removed the communication to the other onelinks, essentially negating the actual purpose of the product... that all detectors should raise all alarms even if its not theirs.. I am happy with my onelinks and that they work with each other. I can demonstrate that to the family and that provides relief to them. At the same time, I have to be honest and say the insteon integration with the smokebridge, as a function of its design, is thin and limiting. Paul

Sorry guys. I accidently deleted the post doing too much at once. That was my thought, that the battery alert is local to the sensor, and might not get transmitted. The design of the smoke bridge does not allow it to receive the unit specific messaging from the FA Onelinks, just broadcasts that affect all integrated units. From what I can observe, you will get an alert from the linked sensor not the rest. Paul

These are the steps Teken is referring to Follow the steps under Replace Modem (PLM)