MrBill

Yea, I left them for clarity (and because I'm lazy and didn't want to redo them all---it's easier to just copy and paste ?) Like you tho, I would remove them.

About 40 feet as the distance to the first z-wave device is probably too far by about 8 times.. From what I've read in this forum 5 feet or less to the first z-wave device is preferable. Good luck with whatever choices you make!!

At first I didn't think your method would work... but after trying values in my head for awhile, it might actually.... I'd write it with positive rather than Not (or negative) logic tho... If ( $iISY.MonthOfYear is 11 And $iISY.WeekOfMonth is 4 And $iISY.DayOfWeek is 4 ) Or ( $iISY.MonthOfYear is 9 And $iISY.WeekOfMonth is 1 And $iISY.DayOfWeek is 1 ) Or ( $iISY.MonthOfYear is 5 And $iISY.WeekOfMonth is 5 And $iISY.DayOfWeek is 1 ) OR ( $iISY.MMDD is 1.01 ) Or ( $iISY.MMDD is 7.04 ) Or ( $iISY.MMDD is 12.25 ) Or ( $iISY.MMDD is 11.01 ) Then $iException Init To 1 $iException = 1 Else $iException Init To 0 $iException = 0 Note that I also removed the Time the program runs from the top of the If statement, that's because we don't actually need it. (being able to remove it make the parenthesis easier too, which is how you likely got caught up in using negative logic. So how do we get the program to Run? Two options to choose from: Run it as the last statement of the Set Date Variable program --or-- Note that the last variable set in the Set Date Variable setting program is $sISY.MMDD = $iISY.Date_Scratchpad which is a State variable. (since it's the LAST state variable set by the program, the change to the value indicates to the ISY that all the other values above it have already been set for today. We would only want to use this method if the last thing the program did was set a State variable AND the value of that variable state changed (each time the program ran). Either of these are great options. So to talk thru the first option, we would probably Disable the Date Exception program, although since it's all integer variables, it would never run on its own. The key to "disabling a program" is that it only disables the IF statement from automatically triggering the program.... A disabled program will still run if it's called by another program... So to implement this we would add the statement: Run Program 'Exception Checker' (if) as the last line to the Set Date Variables program. Then we would right click and the Exception Checker in the tree and select Disable. It will still run everyday because it's being called as the last thing done by Set Date Variables. Talking thru the second option. Lets make one tiny change to the exception checker: If ( $iISY.MonthOfYear is 11 And $iISY.WeekOfMonth is 4 And $iISY.DayOfWeek is 4 ) Or ( $iISY.MonthOfYear is 9 And $iISY.WeekOfMonth is 1 And $iISY.DayOfWeek is 1 ) Or ( $iISY.MonthOfYear is 5 And $iISY.WeekOfMonth is 5 And $iISY.DayOfWeek is 1 ) OR ( $sISY.MMDD is 1.01 ) Or ( $iISY.MMDD is 7.04 ) Or ( $iISY.MMDD is 12.25 ) Or ( $iISY.MMDD is not 11.01 ) Then $iException Init To 1 $iException = 1 Else $iException Init To 0 $iException = 0 Note the RED line, it's the ONLY thing I changed from above. Since I changed one single variable to the State Variable this program will now run EVERYTIME that value Changes. So everytime the Set Date Variables program changes that value, which is a value that does change daily, it will cause this program to fire and the entire IF will be evaluated, even tho all the other variables are integer. What would I do? If I used the second method I would reorder the OR's to chronological as the "exceptions" occur during the year. That readability change would put $sISY.MMDD is 1.01 at the top, and it's easy to spot the "trigger" variable. What I would actually do tho is use the first method, disable the Exception Checker program, add a comment to it that it's "run by Set Date Variables" and then add Run Program 'Exception Checker' (if) to the end of the Set Date Variables program. I only included option 2 as a teaching tool about state variables, but it is a valid option. ----- A note on disabling programs: As you learn more about writing ISY programs you will find many uses for disabled programs. Disabled is actually a tool for when programs run, it's not just a feature that was included for testing. Another user or two were having trouble with disabled programs becoming enabled tho, so i took that as a queue.... I now have a program called "Disabled-intentionally" that has the run as startup attribute set Disabled-Intentionally - [ID 013A][Parent 0001][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'SetpointAdjust-DNchevron' Disable Program 'SetpointAdjust-UPchevron' (abridged for posting..... every program intentionally disabled is listed) Else - No Actions - (To add one, press 'Action') So every time the ISY is rebooted this program runs and makes certain things that are supposed to be disabled actually are disabled.

So what are the error log entries associated with the failures... please feel free to copy and paste!

@rohmerg and @ldb Keep in mind that the ISY error log exists. (Tools > Error log) for each failure you have, there will be one or more specific lines that match up and give more clues about the failure.

There's a lot of confusion in that sentence. The ISY 994i hardware is around 10 years old. The same ISY can be stuffed with a z-wave board or upgrade. The model you have now is not a lot different that the model you had in 2015, except your new one came with the z-wave board already installed. The Alexa interface is a actually a function of the portal. Information can be sent back and forth between ISY and Alexa, but only in a structured manner. and it's fairly limited and must be predefined in the Portal. This was also true with your old ISY. See the thread I link above where someone is doing very similar to what you requested, except instead of an "outdoor outlet" they are using Feit light bulbs--- the concept and instructions remain the same, just with different devices. (which are crappy, don't buy feit). Are you should it was the cold that caused your problem? I suspect it was actually range. When using z-wave one has to build a mesh of devices. they pass the signal on to each other. It's very possible to "get too far away" from the controller or ISY. Here's a post you should review: I'm not sure what you mean, unless you mean one of the Alexa's that has a zigbee controller built into the device. Most Alexa (and google home) devices are fairly dumb, a microphone and speaker. The magic happans because of the Amazon (or google) cloud connection. Without the connection the devices simply don't work (including the zigbee controller built into some) That's not exactly accurate.. see the feit thread I linked above for an example. It is not straight forward tho, and not scalable. The user has to create variables and programs in the isy, create linking instructions in the ISY portal, and then finally create Alexa routines via the Alexa App to make everything talk to each other. I might use it for something like a single set of blinds that Alexa can control, but don't interface easily to the ISY (or without additional expense). But I certainly wouldn't rely of that type of interface for many devices, nor would I do it for something that had to reliably work because it needed to switch on heat when it's too cold. So you mention COLD and Heaters... i doubt that you want to risk control of that to an Alexa (or GH) cloud dependent device. ie. if the internet's down, or the amazon cloud is having a bad day (it happens, not often but the Alexa cloud services have been down twice this year for extended periods, and sometimes she just doesn't do what shes supposed to but if you repeat it works. Anyway I think you want a LOCAL system to control your Heat in a cold enviorment. don't rely on cloud services such as Alexa or GH. That means use your ISY and Z-wave, but you need to back up and understand z-wave limitations and how to get that system to work for you.

I'm not using conbee 2 with Polisy (there's currently no nodeserver), it's plugged into a Pi running Home Assistant, however I can tell you that getting it away from everything else via a 3ft USB extension cord improved its signal to the other side of the house by double. The LQI at the blinds was less than 100 when it was plugged into the Pi directly, reguardless of orientation. Moving it away and higher resulted in an LQI over 200.... (the scale is 0-255).

@WayneUrso This sounds similar to your request: ---- I will ask tho, what type of Outdoor plug is it? If z-wave why not add it to the ISY directly? -- you mentioned in your first post "I recently got the newest ISY994i with Z Wave and Alexa." but you had an ISY in 2015 it looks like from your post history, so I'm a little confused about your history with ISY's, did you have one that died? or did you have a 99i from many years ago and just got around to upgrading to a 994 now?

@guags99 Same info from @Michel Kohanim likely applies to you... perhaps timeouts are the issue for you as well. I don't use IFTTT anymore but I can remember that issue in the past.

The short answer is you need to create programs to monitor each parameter that you want to be notified about. The program watch the sensor and trigger a notification. How proficient are you with creating ISY programs? That's likely your first learning curve..

I'm not sure anyone else in the thread understood until tazman.... He's correct, you need Alexa routines to turn the outlet on and off. those routines need to be triggered via an ISY variable.

If my reply to the OP doesn't also help you, then we need much more information about your setup and what's happaning. Are you in-fact making calls to IFTTT via webhooks? "Me too" posts are often not at all the same thing.

If the same thing works in a browser window (i assume the entire URL the NR is calling, not just the key) then the problem is on the ISY or local network side. Check the error log of the ISY and see if there are more clues there. Have you restarted your ISY? if not, by all means try that. Also your modem/router.....

I'd limp along for now. Go ahead and order a Polisy (from UDI--pro model not needed), Zooz series 700 USB stick (amazon), and a USB PLM from smarthome as time and money permits. Then you can either start moving your stuff over manually whenever you want, and the ISY on Polisy software becomes more stable. With Polisy you can immediately take advantage of nodeservers in your current setup.

Sounds like you already have it done, but if you need help or suggestions just post what you're working on. Of course you can name a variable anything you want, but I might call it $iHoliday instead of $iException. If you haven't discovered it yet, the ISY is pretty cool when it comes to renaming a variable... All you have to do is rename it, the ISY changes its everywhere it's used.

2007... do you have a 994i or a 99i... Asking because I'm honestly not sure of the 994 release date but I thought it was later.

There are several threads on this topic. Your best bet is to purchase the USB PLM, open it and the dead PLM up, and swap the daughter boards. This option is reasonably easy and doesn't require soldering. There's also the option of replacing the capacitors themselves but that required perhaps more tech savviness and the ability to solder which is a learned skill. Third although it's a little bit early in the product life. The ISY-994 is being combined with Polisy on the Polisy hardware. ISY on Polisy supports the USB PLM. ISY on Polisy is still being developed and is in it's alpha stages, although there are several posters in this forum that have "moved over" and retired their ISY-994 hardware. I'd pick option 1 for now, eventually you'll probably want to move to ISY on Polisy, but that's another day....

@SHM By all means also google "ios 15 geofence not working" and read various complaints around the internet. I've been in communication with the developer of the Locative App and he's indicated Apple is being very quiet about the bug. The developers are waiting too. Next navigate to apple.com/feedback and fill out the form with a comment such as "It's a widely know fact on the internet (google: ios 15 geofence not working) that iOS15 broke Geofences when it was released on September 20th, coming up on 2.5 months later it still hasn't been fixed! Why is this not a priority bug?"

include your UUID number from Help > About

Portal is a "per ISY" subscription. Yes Portal works with ISY on Polisy, but you'd need a second subscription. That said... Polisy comes with a 2 year subscription to portal. You may have used that for 994 connectivity, or you may have already had a portal subscription and your included two year subscription is still unused. As far as I know there is no way to redeem that included 2 year subscription without contacting support for manual intervention. Also if you have two subscriptions for awhile, then retire your 994 be certain to contract support so they they can transfer the unused months on the 994 subscription to add on to the end of the polisy subscription.

on https://my.isy.io/ Select Tool > Information > ISY Information. When that URL is used your portal credentials must also be used.

agreed. I don't know what the hardware specs are on the 994's but Polisy's specs "1Ghz Quad Core AMD CPU, 4GB RAM, 32GB 3D NAND SSD, 3 x 1 GB Ethernet ports" likely run circles around the 994.

The first entry "-5 Start" is a reboot. there were two of those here in a row, one at 2:16 and one at 3:30... it's pretty normal to see the entries after the Start, as the system comes up and the network connection is established. Regarding the first post of error log messages, that appears to have something to do with the mobilinc portal, but you probably already guessed that! ?

ISY on Polisy will definitely run faster, however that doesn't speed up related protocols such as Insteon and Z-wave communication... those are slow, because of that it won't seem faster. That's a loaded question! It will support all the Insteon hardware that the current ISY-994 supports. UDI has stated they will not support anymore new Insteon products unless full API documentation is shared by Insteon. They won't go thru the reverse engineering steps that they've gone thru supporting the newest products such as MSII etc. Keep in mind that it's still in development and buggy. It's not even being called "beta" yet, I'd wait until it's been out in beta for awhile before moving over. If you don't have a Polisy tho, yes you should buy one so that you can start using nodeservers with your 994. (IMO, don't buy the Pro model.)

Ahh... i just answered the last question without reviewing the entire thread. I suspect that your polisy is on an earlier version of the OS.... and thus doesn't install the ISY on Polisy pkg. Your fastest method to get up and running with ISY on Polisy might be to open a ticket by email support@universal-devices.com Also ssh to your Polisy and run the command uname -a and copy and paste the output into your ticket.