MrBill

I do have a polisy for local nodeservers, however I'm not actually running that one myself, the cloud version would be better. The problem with the local version of the rachio node server is that it requires and open inbound port from the outside (specifically from the rachio cloud server). I will add that you might be able to get your motion detector to rachio need configured with IFTTT as a middleman. I have a similar need to yours that I run to turn on one particular zone, the hose connections around the pool are actually on a sprinkler zone, so to make it easy I have hidden an Insteon Hidden Door Sensor in a dry outdoor spot. Press the button in and release and it triggers an ISY program , that flashes a light outside (visual feedback), and then calls a network resource, that connects to a webhook which is part of an IFTTT applet that then turns on the sprinkler zone for a 30 minute manual run. It works great... this solution pre-dates node servers, I was going to convert it over to take IFTTT out of the loop if there is ever a cloud version of the Rachio nodeserver.

not sure about using alexa as a middle controller for this, but there is a Rachio node server for ISY, if you're running the nodeserver then yes....

I've had trouble reading those labels lately D and 0 are hard to tell apart, can't think what other letters and numbers but watch the possibilities...

Browser developers have stopped making it easy to click a link to start a Java app. It's too dangerous and most users would probably click a malicious link that installed malware etc. that is disguised as a link for something else. Not gonna name names but if the browser link says "here is your favorite type of cutey kittens, click here" could get you a cute kitten pic AND malware if java is allowed, thats why browser don't launch java anymore. That's why ISY migrated to the launcher, which is not in anyway launched via a browser.

Insteon address look like AA.BB.CC... do you see a product label with address and firmware revision? I don't have any of 2844-222 so I can't say where they stick the label, on the back or possible inside.

You can go to https://my.isy.io/index.htm then click create a new account. this will allow you to create a portal account. You can't connect your ISY to it however, without subscribing to the portal service. The portal account is however UDI's new single sign on service.

At this point in time you keep the existing ISY994, we've heard that someday the ISY functions will likely move over to Polisy. Not sure where the Z-wave controller will be when that day arrives.

It's been noted before but I'll repeat it here. Only a few nodeservers (and most of those are weather) make sense to exist as both local options and polyglot cloud versions. Most seem to be better suited to run local because the other devices exist on the local network, or on PGC because the it's making a cloud to cloud connection somewhere. It also really wasn't hard for me from a time perspective to choose Polisy over Pi. While I have a few pi's around the house doing this or that, none of them are mission critical and none are allowed outside internet access (network rules). The biggest benefit of Polisy to me is that updates are pushed out, and I don't have to do much in terms of systems administration and staying up to date on OS exploits.

It was first announced on Feb 13th.... I read about it in the forum and didn't get an email either... https://www.universal-devices.com/byebyeclimatemodule/

i was just writing a response pointing to that exact example in the wiki

Disclaimer: I don't have the ELK add on, so I could be wrong. my guess is that you want OR for your If conditions: If Elk Area 'Home' 'Arm Up State' is Armed Fully Or Elk Area 'Home' 'Armed State' is Armed Away Or Elk Area 'Home' 'Arm Up State' is not Armed with Exit Timer When using AND it means all 3 conditions must be true, OR means at least one must be true.

Might be brand specific too.... as in some brands may be specific, others may use a simple voltage. Two reasons I can see for a manufacturer to do this. 1) more specific error codes. 2) ball and chain: you can't replace it with a 3rd party product, you're stuck with OEM.

@Michel Kohanim is this not the same battery devices write bug many of us are patiently waiting for to be addressed?

How silly, now they have to stock an additional SKU for paddle color change kits, and brown and black don't appear to be available in the new items color change.

not in browser, however these instructions allow you to run the admin console and connect via the portal.

It's a quick fix... we have to wait for the west coast to wake up tho.

You do have mismatched firmware and UI versions according to your screenshot, to fix that follow the instructions here: That probably doesn't account for the problem you describe however. As for what's wrong with your programs being intermittent I would have to wonder first if you've introduced a noise maker or signal sucker. Meaning the ISY is working just fine like it always has, but the signals aren't getting from the PLM to the device. I think this because if you say they used to work, it's the most logical reason they would become intermittent. Have you changed where they PLM is plugged in? Any new not necessarily home automation related devices. my wife once bought an air ionizer at a thrift store.... that thing made so much powerline noise that nothing worked at all when it was plugged in. We also used to have a deep fryer that when plugged in would kill Insteaon signals.

there is an expired certificate this morning, hold tight, it will be a quick fix once the west coast wakes up... it's still 7:30 in that part of the world.

In my system, I use a program that turns on the barn lights inside and out when the door opens after sunset, however after a certain time they won't turn off when the door closes, they stay on until manually reset. If it's after the specific time, it also rings the back doorbell 3 times, 5 seconds apart. The gates coming into the yard will also ring the back doorbell once if opened between sunset to sunrise.

Same here.... Paging @bmercier?

Have you tried this: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console

Mismatched. Follow the instructions here:

Do you have any idea what firmware version your ISY is currently running? Have you not updated firmware in 7 or 8 years? or am I reading too much into your wording? The best method is the Launcher, It will automatically match the UI version to the firmware version. Instructions are here:

$Fireplace.down.cycle = State Variable '#1704 / Downstairs Fireplace' Temperature = Wireless tag Temperature Node '$Fireplace.down.setpoint Fahrenheit'Is = State Variable If you don't want to have an override switch, you could skip $Fireplace.down.cycle There is actually 3 more programs that work with these 2 for a group of 5. Essentially there are 2 buttons on a 8 button controller that are controllers for the scene. 'DN Fireplace#' is also a responder to the scene. The extra "status" line in the IF of the cycle-on and cycle-off programs takes are of updating when the scene is turned on / off via alexa, or an iphone APP. the single Status is perhaps all that's needed, except this forum taught me to use Control in If's early on.... then when Alexa came along I added the 'status' lines also. I actually have another set of 5 programs for another fireplace.... these have worked very. Haven't needed delays, the temps only update once per minute. All 5: =================================================================================== Fireplace-Downstairs - [ID 007C][Parent 0001] Folder Conditions for 'Fireplace-Downstairs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Fireplace-cycle off - [ID 0078][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature >= '$Fireplace.down.setpoint Fahrenheit' And 'DN Fireplace#' Status is On Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-cycle on - [ID 0079][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature < '$Fireplace.down.setpoint.hysteresis Fahrenheit' And 'DN Fireplace#' Status is Off Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-off - [ID 007B][Parent 007C] If 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched Off Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched Fast Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched Fast Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' Status is Off Or 'DN Back Door Recessed+# / DN All Off' is switched Off Or 'DN Back Door Recessed+# / DN All Off' is switched Fast Off Then $Fireplace.down.cycle = 0 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-on - [ID 007A][Parent 007C] If '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched On Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched On Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' Status is not Off Then $Fireplace.down.cycle = 1 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Setpoint hysteresis - [ID 00E4][Parent 007C] If $Fireplace.down.setpoint < 80 And $Fireplace.down.setpoint >= 60 Then $Fireplace.down.setpoint.hysteresis = $Fireplace.down.setpoint $Fireplace.down.setpoint.hysteresis -= 1 Else $Fireplace.down.setpoint = 73 $Fireplace.down.setpoint.hysteresis = 72 When the setpoint value changes, and the new value is sane, then set hysteresis value. When the new value is NOT sane, set default values.

I'd separate this into two programs so that it can turn on at >= 90 and off at <88 or somethings. With only a single program two things come to mind the fan would go on/off frequently. Also I'd use and AND in If's to prevent excess traffic because each time the temp changes on or off is sent regardless of whether it's already on / off. Here's examples I use with my fireplace: Fireplace-cycle off - [ID 0078][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature >= '$Fireplace.down.setpoint Fahrenheit' And 'DN Fireplace#' Status is On Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') Fireplace-cycle on - [ID 0079][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature < '$Fireplace.down.setpoint.hysteresis Fahrenheit' And 'DN Fireplace#' Status is Off Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action')