apostolakisl

You can restore the new PLM from your orirignal ISY or the new ISY. I did it this way when I switched to a z-wave ISY a couple months ago. 1) Create backup of old ISY 2) Unplug old ISY/PLM and plug in new ISY attached to new PLM 3) Log into new ISY 4) Update firmware if necessary to same firmware you were running on old ISY 5) Restore Backup you created 6) Restore PLM from new ISY 7) Send ticket to UDI giving UUID of old and new ISY and request transfer of modules. In my experience they transfer the modules within the hour. Security Certificates (if installed) need to be re-installed manually. There are a few other things that need to be done manually, I forget what, but check the configuration page and make sure things like time zones and stuff are correct.

I agree, I don't need any cutesy personality from my device. I prefer "OK". Better yet would be a single syllable answer like "done". The cutesy thing is great for TV ads and tiresome in regular usage.

Very much agree with the dot deployment efficiency. I have 3 dots, and may get more. I have one Home and am not likely to get more. Also, Home does not do bluetooth. The hardware is in there, but there is no software to use it. So, unlike my dot, I can't connect Home to bluetooth speakers. Perhaps in a future firmware update we'll get to use the bluetooth.

This particular one is from a 3rd party Amazon marketplace seller (Phenter Sales). Those come and go, so it may not be the same as your past purchases.

5.x is alpha. It can be downloaded if you go to the forum front page and scroll half way down you'll see a developer section.

I have a dot and a home. 1) I get free music on Amazon since I have Prime. Home requires a new subscription. 2) Home is way better at answering questions. Just like OK Google on your phone. Alexa is not very good at generic questions at all. 3) Alexa is good for ordering stuff from Amazon. Home doesn't have any way to buy stuff from it as far as I can tell. 4) I haven't messed with the ISY portal. I assume both work about the same? I'll let someone else address that. 5) I have IFTTT working with Alexa. I haven't tried with Google.

So you are saying V2.2 has (at least per SH) fixed the problem? I sent an email to the seller asking what version they are selling.

Are these the PLM's that supposedly have had the under-powered caps fixed on or are they clearing out the old inventory? Anyone know the exact version number that supposedly is fixed?

You'll need to either 1) Upgrade to 5.x since you can't access system time in 4.5.4 as something to set a variable to 2) Load the set of programs I wrote that puts the date into variables, then you can use those values to set your boot time variables. https://wiki.universal-devices.com/index.php?title=ISY-99i_Generic_Calendar_Using_Programs_and_Variables And you'll also need to add some programs to set the time. I also wrote those, but don't have them posted to the wiki. But they only self correct once per hour, so you would need to put a delay of 1 hour in your program that sets the boot time variable and then know that the boot was actually an hour earlier. Or just subtract the hour back out with more programs. In summary , 5.x is easier.

The above then section is perfect. But I wouldn't do the If that way. At midnight the program will reset and you won't end up with your 1/5 thing. Probably it doesn't really matter, but in the interest of doing things the best possible way, I would do something like IF From 9 am 5/24/2017 (or any other time in the past) To 9 am 5/24/2035 (or any date far off in the future, but not too far i the future since that seems to screw up ISY.) Then what Paul said Be sure to click "enable at startup" in the program summary page. EDIT: Also be sure to right click on it after you save the program and click "run if", this will start the loop. Otherwise the loop won't start until the next reboot.

Do you have any other device that you can temporarily assign that LAN IP which listens on port 80 and 443 for testing? It sounds like you already confirmed that your ISY is actually at 10.1.1.154 and didn't accidentally get assigned a different IP.

Just curious what the reason is for this. And are you referring to the public port number or the internal port number, or both?

I went ahead and made a 20 foot cat6 cable to use as serial between the plm and isy. It appears to be working just fine.

Actually, KPL's are intended for this exact issue. You can do a 6 button kpl, the on/off work the same as a switchlink, and you have 4 more buttons to do with as you please.

I'm not sure I understand what you are saying? If you are asking is it possible to have the switch paddles be separate from the load wire, the answer is no. All commands done by tapping the switch will instruct the load to change as per your action. Obviously, tapping off if it is already off won't cause a change in the load wire and similarly, other paddle commands that would cause the load to go to a state that it has already achieved will have no affect on the load wire. Despite this, the switch still recognizes that a paddle command was entered and broadcasts that command to the network. ISY will see this command and respond to it as your programs have instructed.

You can avoid turning the light on or off. Assuming your load is not in a dimmed state, you click on when on or off when off and have both trip the same program with a then that executes your task. If your light is on, then click on, if your light is off, click off, either way, the same program runs and you get the same "then" executed and the light doesn't change.

Right, but a double top off, when already off is the same as not doing anything. Same for on. You have several options to use a load bearing switch as a trigger without affecting the load. if status on and control on If status off and control off If status on and control fast on If status off and control fast off As I mentioned, you can't use this when a light is other than on or off. I use If status off and control off All the time.

One thing you can do is off when already off, or fast off when already off, or vice-versa. If (status switch x is off and control switch x is switched off) OR (status switch x is on and control switch x is switched on) Then do something The above will let you use a switch to trigger something without changing the status of the switch and it's load. You can also do a fast on/off version of the same program. The only thing is if the light is in a partially on state, then you either have to go full on or full off.

Just to clarify here, IR models have a built-in IR receiver, but not a transmitter. You need to purchase something like a global cache to send ir. Insteon also makes one but it isn't very good compared to GC.

This is what concerns me. I don't want an always on vpn connection through my home when I'm out. Turning it on and off before running apps i want it on for seems like a time consuming hassle. I can just see a friend saying "show me that HA stuff" and I go through 5 minutes of poking around before I can even start.

The google cloud having access to your voice theoretically means they have access to whatever your voice can control and thus so does an intruder. So, just not allowing your alarm to be controlled by voice should handle it. How do you handle keeping a vpn connection going between your phone and home? I have not tried this but it seems like it would be a PITA. I have only done router to router vpn.

Unless the voice recognition part runs locally, I don't see how the cloud can be avoided no matter what. Even if ISY is controlled locally, if your voice gets sent to Google, decoded, and sent back to google home, which then controls ISY, there is still a cloud hack there. I do see the point about the portal. Hack my house, easier, reward is 1 ISY Hack portal, harder, but reward is lots and lots of ISY's. We all know even the biggest of the big guys can get hacked. EDIT: Well now I'm wishing I hadn't jumped on echo. Oh well, maybe I'll get both.

OK. Indeed this appears to be a 5.x firmware issue. I originally thought it was device specific, but I have now tested it on a couple other devices. So far, all devices I have tested on 5.x trigger status programs when progrmatically queried. I'll move this to 5.x forum.

The only issue you may have with this is that your weather module program has no hysteresis. So, if one of the parameters were bouncing around at the threshold level that program would keep switching back and forth. The one I fear the most on that issue is wind. You might consider dropping wind from it. Temp and rain aren't likely to bounce. To add hysteresis you would add a third program that has the other end of a range that is a sort of no man's land. Hysteresis 1 If wind speed is less than 15 then $state.windspeed = 1 Hysteresis 2 If wind speed is greater than 20 $state.windspeed = 0 In the above example, wind speed variable become true (1) when it is less than 15, and false when it is more than 20. In between those values, it retains its previous value. So you would use the variable in your weather program instead of the direct wind speed.

This is the exact program that does what you intended. BackLawnReSeed - [ID 008A][Parent 0089] If From 7:00:00AM on 2017/05/05 To 10:00:00PM on 2017/05/20 And ( From Sunrise + 4 hours To Sunset - 1 hour (same day) And Program 2 is true Then Repeat Every 2 hours Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Start Wait 10 minutes Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Stop Else Set 'Devices / dirNodeServers / RainMachine / RainMachine / Rear Lawn' Stop Program 2 If Module 'Climate' Temperature > 50 °F And Module 'Climate' Total Rain Today < 0.2 " And Module 'Climate' Wind Speed < 15 mph Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Any false trigger in the main program turns off the water or prevents it from starting. False triggers include the aggregate of your weather module conditions becoming false. You end times (sunset or your hard times). It will also turn on with a true trigger. So, your aggregate of weather conditions become true between the designated times. Or your designated start time while the weather conditions are already true.