paulbates

A suggestion is to have 3 programs: 2 programs manage capturing the "If sensor is switched on" for each sensor... and 1 disabled "sub routine" program that handles the wait and turn off the light: Catch "is switched on" from MS, then run disabled program 3 to count down and turn off light Catch "is switched on" from Door sensor, then run disabled program 3 to count down and turn off light Disabled program that waits, then turns off the light The last one that runs the disabled program 3 wins. Edit: having said that, configure the motion sensor to "send on commands only", let the ISY program 3 turn the light off Paul

If you use ‘is switched on’ for the if clause, you won’t need to query it. Paul

I have a program check for the low battery node to switch on and it sends me a notification. Pail

You can go to Tools, Generate Topology. It takes a while, but it will eventually open a browswer window with a list of devices and scenes and that can be printed. Paul

That’s a good point, they all have pluses and minuses Paul

I've had 2 of the Venstar Colortouch's for 5 years. I currently have the T7900 model. I've been very happy with them: Lots of HVAC features Mobile app for my wife to use Remote configuration/management web page for multiple stats / properties Local API - ISY integration has zero cloud involvement I also have 3 of their remote sensors: 1 on opposite living spaces for each stat, and one outdoors shared between them It uses the Nodelink Nodeserver Here's what Nodelink provides the ISY for use in programs Paul

My answer was to put an old access point in the detarched garage that had line-of-sight to dual band devices in the back of the house. A range extender, lamplinc, etc, will do the same thing. I have 2 iolincs in the garage and they work fine this way. Paul

I don’t know how to do that. I sold my 2413U on the homeseer board and bought a 2413s. There may be a sale this week, I haven’t looked. Also from my note yesterday, you don’t want to do this ‘big bang’. Run both side by side and migrate scenes and make new ISY programs one room / function at a time at a pace that you can manage as you learn. Pail

Glad I could help. I had 2 different RCS x10 stats that I had to replace ? check things out and if you decide to migrate, do a little at a time, room/function as opposed to Big Bang, as the isy has its own way of thinking. But once I got it down, functions are implemented relatively quickly. Paul

FWIW, I migrated to the ISY for similar reasons. It turned out to be less work for me to migrate from hs2 to the ISY from hs2 to hs3. The ISY thinks differently.. there’s pluses and minuses. This is only one of a list of things to consider. Paul

Hi and welcome to the udi forums! You can, free of charge, open a port I your firewall and access the ISYs web pages and admin console over the internet. These pages are basic and many people opt for an additional charge app of which there are a number of choices. I migrated from homeseer 4 years ago. Paul

Negative my last. I believe you can use "replace with ..." Install the new remote and name it the same plus a 1 or something on the end Right click on the old remote and pick "remove from folder" Put the new remote in linking mode by pressing and holding its set button Right click on the old remote in the root folder and pick "Replace <old device> with <new device> Let it finish Test Single click on the old remote, press delete Rename the new remote by removing the 1 at the end so the new one has the same name as the old Paul

Skip this, read my next post I don't think wireless devices are supported by the ISY's "Replace Device with..." function. What you can do: For scenes, you can put the new remote in linking mode and add the new buttons, one at a time, to the scenes that the old remote supported. For programs, you'll do a similar thing.. right click on the main program folder and pick 'find and replace' to replace the buttons one at at time in programs. Then simply single click on the old defective remote, and press delete to get rid of the old device and its presence in scenes I'd back up before, and after... and test everything. Paul

Agreed its likely a program. An additional thing you can do is wait for it to happen, and then go to the admin console, programs tab and then summary tab. Click the "Last Run Time" column heading twice so the arrow is pointing down. The list will show the most recently run programs at the top. If a program is doing this, it will have run recently and be near the top of the list.. look at those first as culprits. Paul

There's a couple of things that need to happen and a controller with the ISY's capability will be needed with these components: The valve needs low voltage ac/dc to stay open Did you get a powersupply for it (11 - 15V AC/DC)? On/off outletlinc or appliance module plug the valve's powersupply in, power and control it PLM on the ISY to control the outletlinc Wireless tags send a network message Wireless tag configured to communicate with the ISY (or nodeserver) An ISY program to detect the message from the wireless tag control the outlet Notification to you that something happend Paul

I set up a gmail "house account" that I use for this and also for the login emails to my online accounts; ISY, Venstar, Rainmachine, Pushover etc. You may have to try a few times to find an accout name that works as many are take. This way, you can leave your personal account security settings high, Also, if you sell your house, you can simple turn over the account and not have everything tied up with your personal account Paul

Yes. That’s how I do it. Paul

Configure you SMPT settings so gmail is your primary server, not ISY. The directions are in the link You'll also need to: Allow less apps in your google account: https://support.google.com/accounts/answer/6010255?hl=en Make sure every notification has text in the subject line and body Paul

It goes back a while, but the recommendation is to not use the ISY default mail service and configure the mail services directly. Its mentioned in the wiki. It discusses how to configure gmail. A number of other providers configurations are available in the drop down in the admin console. Paul

I still have 3 of them outside and have settled on proactively changing the batteries 6 months apart in the fall and spring, without waiting for the alert Paul

In addition to the others comments which resonate with me, my understanding is that you take Polisy out-of-box, plug it in and quickly getting it talking to an ISY and up and running on polyglot and nodelink. No raspbian install, unix config, unix commandline to deal with, etc. I believe the larger looming ISY audience wanting to adapt V5 Nodeserver capabilities will not want to have learn enough linux/pi to get by to have nodeserver capability (like I did). When UDI flips the switch on general release V5, I see a lot of people going this way. I also believe it will be the ISY 994i replacement in the future, and look forward to the day that my HA is running even faster. I'm looking forward to mine (pro). Paul

Hi and welcome to the udi forums! Go to the programs tab. Look for the program that sets the scene at the certain time. Click on the “if time” statement of the program and adjust the time to fit. Paul

Same. It can be used standalone with the RainMachine app and also some enhanced functionality with the ISY using v5 firmware and Nodelink which can be looked up hear on the forum. The enhanced functionality includes dynamically changing field capacity (# of days between watering) in the spring and fall. Also I have a “hot zones” schedule for sunny areas and have the ISY dynamically kick it off under certain conditions Due to its features and internet wx that control if/how long watering happens, it paid for itself and in the first year in lowered water bills.(our Detroit water is expensive). I don’t use an ISY mobile app. For spring / fall maint I use the RainMachine app to control zones. Paul

I user the filters on column A and B to narrow down what to look at, or filter out background noise. Control1 ... N in column b can be filtered out Paul

To Larry's point, new ISY's are being shipped with Version 5 of ISY firmware. If you are using the version 4 admin console for your old ISY, that probably explains the problems you are seeing. If you use the new ISY Launcher to launch the admin console, it will figure it out automatically