MrBill

it's on the Configuration tab.

You can write the If statement just as you have and anytime any of the variables change it will evaluate all conditions and possible run the THEN block, Warning tho, this is a the exact type of program where users get surprised by how often Else Run. You indicated "else do nothing" which is great, but keep in mind that anytime any of the values change or are updated either Then or Else is going to chosen to run, else.. nothing is perfect in this case. If those values update often you might want to add: IF $sAQI >= 50 And $sDEQ < $sAQI And Ventilator status is Off then Turn on ventilator.... Depending on what platform controls the ventilator this may cut down on extra traffic... i.e. the ISY telling the ventilator to turn on frequently when the ventilator is in fact already on. Note: if the outside air quality is irrelevant for triggering the routine... that is it's only a filter that might prevent the on trigger, then you might make DEQ an interger variable instead: IF $sAQI >= 50 And $iDEQ < $sAQI And Ventilator status is Off then Turn on ventilator.... by doing that the IF is only getting evaluated when sAQI changes, however the current outdoor can value DEQ is still used to determine whether to fire the routine.

@asbril has been successful with z-wave only, he has no Insteon at all. Personally, I prefer many of the of Insteon features that don't exist in z-wave.

Not sure what you're seeing. I'm going to guess tho.... After entering the UUID of the ISY in the portal interface at https://my.isy.io then you would need to approve the connection via the admin console. TO do that open the admin console and go to the Configuration tab, if you see a "portals" tab go there and click Approve. If you don't see the "portals" sub-tab go to Help > Purchase Modules and choose the Portal. Note: UDI's website that opens during the purchase option is weird, you might have to select Purchase Modules again after logging into UDI's website. You may also need to click "My Products" left center of the screen. (Don't click "Store" at the top of the page--that's for hardware.) After the module has been added then you must go to the Configuration > Portals tab and approve the connection.

It depends on your timing, in other words how fast you want to move forward. Today you can buy a 500 series Z-Wave board from UDI and upgrade your current ISY. If you want to wait a bit, then you would buy Polisy and Zooz Series 700 series z-wave stick to go with it. ISY running on Polisy is currently in development. (the polisy hardware is already available for nodeservers and Alpha testing of the ISY on Polisy software. I understand they are pretty close to making z-wave on polisy a thing, but there just not quite there yet. neither option currently supports zigbee.

That would be the solution. It's so much safer and easier to setup. in 2012 I'd still open ports, in 2021 I'd definitely prefer that there is a solution that didn't requite open ports-- for the ISY that solution is the portal, and UDI charges less than $1/month... you can't go wrong.

What kind of programs are you running? One possibility is that you have one or more programs that is a run away or endless loop. You can probably find that looking at the program summary page. How old is your ISY? another possibility is that your SD card is dying, but actually i doubt this one myself. It's definitely not normal to have to reboot your ISY... mine currently hasn't been rebooted in about 2.5 months. If suggestions here in the forum don't lead you to a conclusion soon, you should open a ticket by emailing support@universal-devices.com they'll find the issue quickly I'm certain. I read the forum daily in this isn't a common issue, you may need support, but after you find out the answer please update this thread so that we can use it to help the next guy with the same problem.

I agree with @Javi If this was a 3-way situation before Insteon, maybe the other end is what's actually connected to the light. If that's the case you should make both switch controllers in a scene to keep them in sync.

@pjjameso and @sjenkins There are also "blank" nodeserver templates in the store... see PythonTemplate and NodejsTemplate.

After a nodeserver is added to polisy, you must restart the Admin Console. (that's when nodes get read an created.)

I don't think you'll have any problem. I have a rock solid installation with ISY and HA, i don't use homekit, but i did try it out. there's no gotacha's just dive in and get it going. Not going to give detail instructions based on this post, because it's impossible to tell what stage you're at now. dive in.

Correct, the 994 hardware is nearing it's 10th birthday. The hardware will be supported for years to come, but soon all newcomers will be running only on Polisy, both for nodeservers and the functions that are today built into the 994. The Zooz Series 7 module is how "ISY on Polisy" will speak z-wave. The 994 speaks z-wave using a native board, manufactured and sold by UDI. (the current version is a 500 series z-wave board, while there was once a 300 series z-wave board.) The Series 7 dongle actually means 700 series z-wave.

Use 5.3.4 even if tho it's labeled test build, it is stable. The problem with "official" labeling in the 5.x branch is that UDI has to pay out (rumor is in the $10K range) to have a release z-wave certified. Therefor there's only one 5.x release that's labeled official. there's two or three releases after that are labeled "test build" but are really more like "bug fix" releases. "Test build" after the "official" is better than 5.0.16b which is a "beta build".

For the app issues, set an IP reservation on your router so that HA always gets the same IP address. I used to have problems with the iPhone app but don't so much anymore, I think that is the difference. Be sure to install the Google Drive Backup Add-on, It just works...

It sounds like a problem I had with another nodeserver a long time ago. The formatted values were staying numeric as you've shown in your second example. The answer for that particular situation where the data is being converted from a numeric to string value was that it wouldn't do it correctly until the ISY was rebooted/restarted after the nodeserver install. This is not the normal restart the "admin console" after installing a nodeserver, this is reboot the ISY after installing a nodeserver where the formatted value is a string. That all boils down to "has ISY been restarted since installation of that particular nodeserver?" if not, try that.

I think you want these to be joined with AND $iToday is not $iNewYear Or $iToday is not $iMemorial Or $iToday is not $iJuly4 Or $iToday is not $iLaborDay Or $iToday is not $iThanksgiving Or $iToday is not $iChristmas Or $iToday is not $iFloat lets assume $iToday = 329 (i.e. thanksgiving) if we make a truth table out of the statement above it is (True or True Or True or True or False or True or True) which results in True on the other hand, joined with AND you would get a false on thankgiving which would result in the ( False) for the overall statement. On a day not listed all would be True. ----- All that said... I'm going to suggest a better approach.... Add this program from @kclenden... -- then since you're wanting to use dates as filters you would want to use the $i____ version of the variables in your If statement. Use the $s... version of the variables when you want to Trigger the IF statement, use the $i.. version of the variables when you want to filter of stop the running of an IF statement. Note: thanksgiving is the 4th Thursday of November or when ($iISY.MonthOfYear = 11 AND $iISY.WeekOfMonth = 4 AND $iISY.DayOfWeek = 4 ) ---- Actually I'm going to repaste @kclenden's program with a minor change: Set Date Variables - [ID 0104][Parent 0126] If Time is 12:00:00AM Then // Determine Day of Week $sISY.DayOfWeek = [Current Day of Week] $sISY.DayOfWeek Init To $sISY.DayOfWeek $iISY.DayOfWeek = $sISY.DayOfWeek $iISY.DayOfWeek Init To $sISY.DayOfWeek // Determine the Month // $sISY.DayOfMonth = [Current Day of Month] $sISY.DayOfMonth Init To $sISY.DayOfMonth $iISY.DayOfMonth = $sISY.DayOfMonth $iISY.DayOfMonth Init To $sISY.DayOfMonth // Determine the Month of the Year // $sISY.MonthOfYear = [Current Month (Jan=1, Feb=2, etc.)] $sISY.MonthOfYear Init To $sISY.MonthOfYear $iISY.MonthOfYear = $sISY.MonthOfYear $iISY.MonthOfYear Init To $sISY.MonthOfYear // Determine the Week of the Month $iISY.WeekOfMonth = $sISY.DayOfMonth $iISY.WeekOfMonth -= 1 $iISY.WeekOfMonth /= 7 $iISY.WeekOfMonth += 1 $iISY.WeekOfMonth Init To $iISY.WeekOfMonth $sISY.WeekOfMonth = $iISY.WeekOfMonth $sISY.WeekOfMonth Init To $iISY.WeekOfMonth // Create Month.Day Combo $iISY.Date_Scratchpad = $iISY.DayOfMonth $iISY.Date_Scratchpad /= 100 $iISY.Date_Scratchpad += $iISY.MonthOfYear $iISY.MMDD = $iISY.Date_Scratchpad $iISY.MMDD Init To $iISY.Date_Scratchpad $sISY.MMDD = $iISY.Date_Scratchpad $sISY.MMDD Init To $iISY.Date_Scratchpad Else - No Actions - (To add one, press 'Action') In my version "Week of the Month" does the inline scrathpad calculations using the $i or interger version of the variable. In the original version the scratchpad calculations were done with the $s or state variable. Since anytime a state variable changes it will run IF statements the original resulted in a weird occurrence that was related to thanksgiving. (I'd actually made two mistakes but discovered the improvement documented here while tracking the cause down.)

I heard they discontinued everything... old line and new... they're going out of business... you said so yourself! ?

I ended up starting over after about 2days... that is I learned, made mistakes, learned somemore, then when I had a better idea what was going on, I used balena etcher again to start with a fresh clean image. It should find the ISY when you start it up. You;ll need to configure it tho. Configureation > Integrations. If the ISY is not found click Add Integration in the lower left and type "ISY" on the search line...

All of my automation were built in the ISY long before HA came to my house. Generally my rule is that if the device is connected to the ISY I do whatever automation programming i want in the ISY. Likewise I now have some shades that are zigbee and connected to HA. The automation for those are built in HA, they close at Sunset +30, open between 5am and 9am when both iPhones have been disconnected from charging. Although I also built a method for the ISY to control it... as there is an Insteon button that is a manual override. In reality I find ISY programming to be more organized... well at least the old fashioned way... FOLDERS... HA lacks folders but does have filters and search for quickly finding automatons. There's also Node Red available on the HA side (install the add-on) but I haven't needed it yet so I've yet to experience the learning curve. Speaking of HA add-on's, it sounds like you have HA up and running... be sure to install and configure Google Drive Backup to do a full backup every night.

I'd recommend opening a ticket, if your polisy hasn't been getting used there are several updates that are beyond simply clicking the update now item on the menu. support@universal-devices.com Other than that, here is the getting started guide: https://www.universal-devices.com/polisy/

@Schlyguy sells recapping kits on ebay. They do ship from Canada, mine arrived in a week. https://www.ebay.com/itm/174552309995 There are two version 5 and 7 capacitors. Looks like the 7 cap kit is sold out, but you might ask, When I purchased mine there was only 1 left of the 7 cap kit, and the next day there were 10 more.

Here is the @lilyoyo1 thread I refereed to, it's a great read especially when you are just starting out building a z-wave network.

Also keep in mind that z-wave creates a wireless mesh and you need to build the mesh for proper communications. there's a @lilyoyo1 post thats pretty good on starting out with z-wave.

Upgrade your firmware to 5.3.4 before you install the z-wave board. I'm going to ask the moderator to move your thread to the z-wave sub-forum, what you are really asking here is which z-wave outlet is best.

Since it's a 2413S the path of least resistance is likely the board swap with a new 2413U as Brian mentions in paragraph 3.