paulbates

Its hard to diagnose / fix something that everyone agrees is broken... what difference does it make why a broken program isn't consistent? Try putting parenthesis around the first 3 if rows as oberkc recommended for both programs and test again

That's a great point, I totally missed that. Its working as designed without the first three lines being encapuslated in an "and"

The ifs are kind of a stack.. first condition checked first, then second,... In this case, I would start with the time conditions at the top of both programs so the programs do nothing at all most of the day because the programs will stop thinking once they validate time. I follow that method. There's a number of ISY-isms that you'll need to learn and adapt to the way it works. It will be more productive to focus on what it is, then trying to find out all of the things its not Paul

Hey Andrew If you have harmony you can integrate it directly with Alexa via its skill. Jimbo also has a v5 harmony node server. Both of those use network connectivity to the harmony... no ir required. I use both of those... the harmony skill switches things on/off, controls volume and sets things up”Alexa turn on amazon video”. Jimbos harmony nodeserver can do that as well, but it was less work with the Alexa skill as it already has the spokens built in... no need to write ISY programs for that. Jimbos nodeserver informs the ISY what the harmony is doing so lights, blinds etc can be controlled. Also jimbos nodeserver can control anything the remote does: hdmi inputs, etc. ideally that would all be done with harmony app programming, but if you needed to, you could. Also the portal allows Alexa av control but I’ve not used that, hopefully someone who has can discuss that. Paul

I use a combination of raising or lowering humidity setpoint relative to outside temp. I also automate hvac fan cycling so if there’s a long time between heat cycles, air is moving in the house. I have two non automated humidity & temp sensors I’ve moved around the house to see if humidity is a problem low or high. The only place it can collect for me is the attic, and there it’s not bad, just a little high. I kick on my attic fan at low speed for a period every 1.5 hours humidification is active, and then a run out period that happens 2 hours after the last humidification cycle completes. Paul

Depends a little on the wiring, but the micromodules could possibly installed at the destination fixture instead of in the switch box. See the manual, page 5. You'd install it at the first fixture in the case of multiple fixtures on one swtiche

Hi Bill Yes, that will work For installation, you'll need to add it to the portal account while its online and use the Configuration/Portal tab to initiate the conversation from the second ISY Yes, infact you want to. The PLM's Insteon address is unique in the world and to your network. When you restore the other ISY's backup on to the new ISY, that PLM needs to be attached to the new ISY. Its due to the relationship between that particular PLM and devices on Insteon network. These are the tricky topics For the IP address: if your Nodeservers are running on a local rpi (or other local server), then it will be critical that the new ISY get the same IP address as the old ISY, and that the Old ISY get a different one, if you plan to run them both at the same time. You'll want that in place before you restore the back up. For the UUID: What kinds of things have you done with the portal? If you've taught it alexa spokens or used Portal based Nodeservers, those will be tied to the UUID of the old ISY. For some items in the portal like Alexa, you can download an excel compatible CSV file that will document your work. I don't believe it can be re-imported, you'll need to re-enter those items. For using X10 with the optional X10 module: If you have A10/X10 Experimental Support module installed on your old ISY, and you used its features to name modules, you'll need that module on the new ISY before restoring the ISY backup. If this is the case, you have the optional module, UDI may consider transferring the licence, open a support ticket, state this is what you want and clearly define the old and new UUIDS Paul

Great! glad to hear it.

Here's an example of where in the portal to add it. I'm assuming your hvac fan would be in there as a device. If not, you can use the program method I mentioned above. Create the program, add it under program in the picture Paul

Hi and welcome to the UDI forums! I don't think alexa thermostat skill can control an hvac fan directly. However, you can create a program for this and use that with the spoken in the portal if <nothing> Then set fan on (you'll need the correct device node for your zwave thermostat, this is a sample) Else set fan off This assumes you have the ISY portal and associated your alexa devic to it Edit.. If you zwave thermostat shows up in teh portal as a device, you can skip the program and associate on and off from the portal. Paul

I'm doing it with the thermostat. It works best to read humidity in the living space. Then, to your comments, engage the humidifier when the humidity is low. I've found over 4 years of doing, that heat and humidity have lives of their own and running separate humidity cycles helps even humidity, and that has improved our health and not feeling uncomfortable and dry. Since the furnace usually offers 24volts to power the water valve, I'd probably use the iolinc, but either is fine. Some other things: Plumb the humidifier to hot water, so when you're running a demand humidity cycle, the water is more ready to evaporate vs when hot air is moving through. I have 2 furnaces / aprilaire humidifiers and wrote programs that track runtime in humidity mode, and then by detecting excessive runtime, send a notification that the pad is gunked with calcium (we have a limestone aquifer) I have programs that scale the humidity up and down relative to on property outside temp to prevent window frosting I also have programs vent the attic periodically when humidity has been active so that moisture does not build up there Paul

@Bumbershoot Here is the comparison file of 2 pages. It was here on the forum. Its a before and after turning the breakers for the signalinc on. Paul Insteon Bridge.pdf

I’d have to dig out the doc later this week when I’m back home, but I’d did a before and after “throwing the breakers” view of device hops using Mark Sandler’s homeseer Insteon plug-in when installing the Insteon signalinc in my panel. It made a large, measureable difference that I can show. Mark’s plugin has a device by device signal performance and hops consumed report that I ran several times before and after turning it on. Rf bridging consumes hops, while the signalinc passively puts all powerline devices as PL neighbors. I don’t see it as a longevity play, just another way to strengthen the network. Having to work in the panel makes it a pain to install Paul

I have the distant ancestor of this one. I put mine in in the 2002 time frame, it has 2 LEDs lights instead of one, but same package and idea. Edit: Mine is a surge protector... that's what I meant. The key feature is managing surges. Paul

I've had good luck with PLMs as well. If starting over in a new house and using Insteon, the I would do these things Have a whole house power conditioner installed in the panel. They cost ~$125 + installation. I would do this with any PLC technology; its an insurance policy for any/all electronics. If you can find one, also install a phase coupler. The Insteon signalinc wired coupler is no longer available, but this is the one I would pick today I agree that a lot of people have reported problems in "the thread" and that there have been regular requests for help here that get debugged as a broken plm. At the same time, there are people that don't have problems, and chances are that they don't report in that they are working. We don't have real stats on the members that don't have problems or the percentage of each. Paul

Glad you made progress. Its one of those things that it can be hard to achieve, but once you get past it you can forget about it and it just works. I followed generic directions similar to what io_guy posted above, but they were specifically for the pi. I've had nodelink for a while, preceding his "all in one" script. At that time I hunted around the forums and Rpi docs and worked it out that way. This one took me a little time because I'm not experienced at linux either, just enough for basic administration tasks. Paul

Hi Dave There's 2 methods on the linking menu to add devices Start Linking - where you tell the admin console to wait for insteon devices to be locally put in set mode Add New Insteon Device - where you type in the Insteon Address to start the linking conversation from the ISY Whichever one you tried, try the other one and see what happens Paul

It looks like these last parts didn't take: ### Creating directory mkdir: cannot create directory ‘/home/pi’: Permission denied bash: line 31: cd: /home/pi/node: No such file or directory Your user account doesn't have the rights to create the directory to put Nodelink in as specified by the script. Create another directory where you'd like to put Nodelink, with an account that has the right privileges ### Downloading NodeLink /home/pi/node/NodeLink.exe: No such file or directory Since the directory couldn't be created, nodelink can't be downloaded to it. This command should do it, when executed from the directory you intend to put nodelink in: wget http://automationshack.com/Files/NodeLink.exe ### Modifying startup script sed: can't read /etc/rc.local: No such file or directory sed: can't read /etc/rc.local: No such file or directory This is where the script sets up nodelink to start when linux does. This will be dependent on your version of Linux, and the directory where you downloaded NodeLink.exe. Also, if you use sysctl, etc. I don't know this so don't have specific advice on how to complete it. Paul

It will be a little slower, but you can force access via SSL, get into the console that way, and set the port back Add an entry to your same IP address, with :443 at the end: Once you get in, go to configuration and return your http:// port back to 80. Your ISY will appear in the finder once again and you can delete the manual entry in the finder Paul

You are on the right track. What you need to do is add a program that sends any temperature change to a variable. This program will run independently and capture every change in temp immeadiately and send it to a variable, so you can compare it in your original program Pick one of the 2 devices. Let's use the thermostat current temperature reading Create a State Variable in the Variables tab. Call it Room_Temp_Hold (or whatever you like) Create another program that will capture any changes in temp, when it happens, and send it to that variable. As an example, this is mine for my outside temperature HVAC Outside Temp to Variable - [ID 006F][Parent 0017] If 'HVAC / Outside Deck' Temperature < 150° Then $HVAC_Outside_Temp = 'HVAC / Outside Deck' Temperature ° Else - No Actions - (To add one, press 'Action') Out side temp is used for a number of HVAC purposes. The outdoor Venstar wifi temperature sensor is located on the deck, under the decking table near the grill. This program insures that the outside temp is populated to a variable so it can be compared in programs that need it. Each time the outside temp changes 1 degree, this program is called and updates the variable. To change my program for your use: Where I have Outside Deck, you put the node for your thermostat temperature read point Where I have $HVAC_Outside_Temp, you put the name of the variable you created in the first step above The 150° just provides a value that can never be reached... it makes sure the program captures every 1 degree change in the variable, right when it happens Then, for your original program, do this: IF thermostat setpoint is < than $Room_Temp_Hold THEN turn something on (like the insteon 2450) ELSE turn that same thing off That should do it. Note that the first program only runs on changes from the thermostat. That's important because you'll have to wait for the first temperature change from the thermostat for a valid value to show up and the new program to run for the first time. This will be true every time your ISY reboots (eg power blip). There's a way to address this with the ISY's variable Init function, or by running the first programs "then" in an ISY startup program. But I've never found it to be a problem. Paul

There’s an option on the Configuration tab: - Catch up schedules at restart -check box - Missed schedule grace period in minutes and seconds. you can ask the ISY to travel back in time as far as the value that you set , at restart i’ve not used that. I try to make my programs as resilient as possible paul

Have you tried factory resetting followed by a restore device? Paul

This spacing is sometimes needed because X10 and Insteon share a very close powerline frequency for signaling which interferes with each other. When Car Remote.b is sent, there is likely an Insteon acknowledgement(s) sent in response. The ISY doesn't know this and will send the X10 A15 right away and it will collide with the Insteon acknowledgement (or Insteon re-stransmissions). X10 does not have message resilience built in, so the send A15 is "stepped on". The Wait command accounts for that in this case, the OP has a program waiting for an inbound X10 signal. There'll be no related Insteon traffic at that time Paul

Michael, Its Echo specific. Rob, take a look at this thread. You may have to search around more in the portal section of the forum Paul

Les For the programs that are not reading the sensor, I'd suggest taking out the from / to range. These 2 programs don't need that: Turn on at sunset: Have a program check for sunset only , turn on 30% After 11pm: Have program check for 11:10 pm only, turn off Paul