paulbates

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

Mark, take a look at this post (similar problem) and the one following it. Follow the same pattern for the directions and the backup should work. Also read this: If you have windows but don't have telnet: Install Telnet on Windows Click Start. Select Control Panel. Choose Programs and Features. Click Turn Windows features on or off. Select the Telnet Client option. Click OK. A dialog box appears to confirm installation. The telnet command should now be available from a command shell window Paul

I don't have any problems with them. Cons: The screen can be a little overwhelming to the family as opposed to a Nest. But my approach is for the thermostat, sensors and ISY programs to keep the house comfortable so that no one is wanting to change it. Probably my most complex programs determine how much cycle time for the fan to keep temp in check based on external temp and temp difference between floors. Also, if you turn on the cloud feature (separate from local api), the app can be used to control it. It took time to get used to configuring it when calibrating stage 2 kick in for heat. The 2 areas of my house, each with HVAC system and thermostat, required different deadband degrees / delay time. Also working how much humidity to deliver without frosting windows. I used the runtime programs posted in nodelink to observe how hard each system was working for heat and humidity. Once I had it set, I haven't touched either in a number of years. Paul

Nodelink is another node platform. It requires .net. I use a Pi and Mono. Its one exe, a very install via a provided install script. Its one exe and a config.xml file which the web interface maintains. I have both polyglot and nodelink on a single RPI 2B, which is taking a nap on that load. I have 2 thermostats and 3 wireless sensors : 2 internal, each installed in living spaces on the opposite floor than the thermostat, set to averaging between thermostat and sensor. 1 external installed on my deck and shared between the thermostats. The thermostats use the external temp, and the ISY can read it to anticipate high heat or very cold affecting the living spaces. I also use it for the ISY to kick off a "hot zones" sprinkling program Here are some images: One thermostat's nodes Runtime node Wireless Sensor Node Paul

I’ve been using 2 venstar colortouch T7900 thermostats for 4+ years. Local only api, reasonable hvac depth (humidity control, multiple heat cool stages, configurable stages calls, wired and wireless sensors- indoor and out... more). My wife uses the app to control temp, it supports Alexa. I use ISY firmware v5 and nodelink to control them. There’s a significant amount of features ISY programs can control. I’ve seen them for $170 delivered https://venstar.com/ Paul

Udi has been clear for several years that they’d include the ms II based on provided specs and popular demand to include it. They can’t make the sensor work. This discussion needs to be taken up where it belongs.

Not sure if Larry’s advice fixed it... if no; Are you sure the expected programs aren’t “stepping on each other” ? Disable all but one and retry. Also, if you have scenes and programs for the same function, that could be causing it Paul

- One suggestion is to verify that its not something else, e.g. the problem is not a program. What happens if you use the ISY admin console to: Turn the device on / off directly? Turn the scene on / off directly? Same behavior or different? - Another suggestion: There's a way to get the program(s) to reveal when they've been run, you can use this after recreating the issue: Go to the programs tab in the admin console Click the Summary tab to the left Find the Last Run Time column in the table Click it twice so it shows the most recently run programs on top Test the switch to recreate the issue, then press the refresh button on the right the program(s) will be on the top of the list Paul

Good point, I missed that one. The ISY needs to be factory reset prior to that. The updated steps are: Make sure the new ISY has all of the modules (network, climate, etc) the old ISY does Alternatively work with UDI support to transfer the modules from old ISY UUID to new UUID Don't remove or do anything to z-wave on the new ISY at this time. Attach the PLM and network to the new ISY Factory reset the new ISY Restore the old v4 backup to the new ISY, makes sure its running. Add the new ISY to the portal, if there is a portal account, make sure everything's working Upgrade the new ISY to v5.015a z-wave version (not the one with zigbee, etc) Follow the 10 steps under Install on the first post of the V5.0.15 thread Ignore the section about migrating zwave from the 4.x branch since there is no existing zwave on the existing ISY After the upgrade, look through the programs tab for any yellow colored program icons that need attention, usually scene related Sometimes just saving them fixes them backup the working result Let it run for ~ 1 week to make sure existing functionality works. Back it up one more time When ready for zwave devices, configure set up zwave card, etc.

The same task will be ahead though.... the current running v4 environment must needs to be upgraded to 5.x. That is done one of 2 ways: Upgrade the existing ISY to v5, back that up and restore to the new ISY,... or Restore the the V4 backup of the old ISY on to new ISY, and then upgrade the new ISY to V5 I'd recommend #2 and do it this way: Make sure the new ISY has all of the modules (network, climate, etc) the old ISY does Alternatively work with UDI support to transfer the modules from old ISY UUID to new UUID Don't remove or do anything to z-wave on the new ISY at this time. Attach the PLM and network to the new ISY Restore the old v4 backup to the new ISY, makes sure its running. Add the new ISY to the portal, if there is a portal account, make sure everything's working Upgrade the new ISY to v5.015a z-wave version (not the one with zigbee, etc) Follow the 10 steps under Install on the first post of the V5.0.15 thread Ignore the section about migrating zwave from the 4.x branch since there is no existing zwave on the existing ISY After the upgrade, look through the programs tab for any yellow colored program icons that need attention, usually scene related Sometimes just saving them fixes them backup the working result Let it run for ~ 1 week to make sure existing functionality works. Back it up one more time When ready for zwave devices, configure set up zwave card, etc. Paul