apostolakisl

When it is actually on, and you press off, it should do nothing (run the blank else), so you are saying that it is running true and setting the variable to 2, when it should be nothing? This would be akin to me pushing off when the light is on, and having it go off then back up to 25%. My lights do not do this but extremely rarely, and back when I first created these programs, I tracked it and found that the only time I saw the problem is if ISY had the status wrong as being "off" when it was not. If indeed you can demonstrate that for certain ISY had the status wrong, please report to Michel. I tracked it by a program similar to this. If status device x is off or status device x is not off Then send notification device is %status (use variable sub in the custom notify section to put in the status of the device) To complete the tracking If control device x is switched off Then send notification device x switched off If control device x is switched on The send notification device x is switched off If status $s.AL.FRO.Mon is 2 or $s.AL.FRO.Mon is not 2 Then send notification $s.AL.FRO.Mon = variable sub With that series of programs you can track the events. Like I said, the program you wrote is supposed to work per Michel and ISY logic, if it is not, then it is a bug. You might add a system time stamp to the notifications as well just in case the emails pass through the email server out of order.

What firmware are you running? I can tell you that a few versions of firmware did not have it right, I don't remember which ones, but I'm currently using 5.0.10 and this runs it correctly. I use this program type every day many times per day and it works. I have not installed every single firmware so I can't say for sure all the firmware that do not run it correctly, only that the vast majority that I have installed on my isy do it correctly. The other thing is of course if you did a fast off instead of a regular off.

I mean there is no race situation. There were a few firmware versions where there was a bug in ISY code that made this program not work. But neither 4.5.4 nor 5.0.10 have that bug, nor do must others. Over the years as I have updated my firmware and have had these programs, there has been two times that I installed ISY updates that broke this logic. Each time it was corrected with the next update after I pointed it out to Michel. You can't check ISY status after it inappropriately runs and say that "status is correct". At this point it will be correct, otherwise the program wouldn't have run at all (the program only runs when it receives a comm from the device and thus . . .got the comm and will show the correct status). This is a mistake in status from an earlier button press turning it on which ISY would have not received that causes the false running. If the device is actually in a not-off (on) state, and ISY thinks it is off, and you press the off paddle, the program will run inappropriately as true, setting your variable to 2. This is the behavior you describe and is the behavior I, once in a blue moon, have seen in my system and when I put tracking programs on the status of the switch found that this only happens when ISY has the incorrect notion that the switch was off when it was not prior to pushing the off paddle.

This is not correct. If status off and control off Then do something Is logic that ISY handles just fine. It will be true when the device status is off at the time of the off press and it will be false in any other state. The reason your program is not working is almost certainly a comm issue. ISY probably has the device status wrong at the time of the button press. In other words, ISY has the device as being off when in fact it is not. I probably have this same program written on 25 or more devices in my house. I use it as a "night lite" feature. If I am wandering about the bathroom or bedroom area at night, I can press the off paddle on any light and it turns on to 25%. Below is one example of many and they only rarely mess up and when wrong, it is a comm issue. Bath Night Lt. Can - [ID 0076][Parent 0083] If 'Master Bedroom / Master-Bath Cans L' Status is Off And 'Master Bedroom / Master-Bath Cans L' is switched Off Then Set 'Master Bedroom / Master-Bath Cans L' On 25% Else - No Actions - (To add one, press 'Action')

I have my garage doors wired to the Elk. It is of course a never-failed comm. If you have the ability to hard wire back to the Elk panel, then I would definitely do it. Myself, I didn't think to hard wire for control of the door (only status of the door), so I hacked an RF garage door opener and wired it directly to an Elk relay. This works great for me since my Elk panel is easily within radio range. I have never had a missed command in 8 years. Much better than using Insteon comm.

That is just shy of 1 year ago. The question is . . . when did they make the fixes that supposedly take care of the power supply issue?

I see you can do variable substitution with google assistant in ifttt. Trouble is, rest requires 0-255 as the range, not 0-100. I don't see any way to rescale that. Maybe instead you have it do a rest command to a state variable in isy which triggers a program that resclaes it then (using 5.x firmware) sets light to that percentage. But that just seems like a lot of complexity.

OK, just created my first IFTTT for my google home. It is better. A lot more options. Unless Alexa has updated since I created those around Christmas time.

I'm sure what you meant to say is that "I'm sure I'll get less immature with age"

Echo tells you what its going to do also. "Amazon, trigger kitchen lights on" Answer "OK, sending that to IFTTT" "Amazon, play Smashing Pumpkins", Answer "OK, here is a mix of songs by Smashing Pumpkins" As I mentioned, Google is definitely better at answering random questions about who knows what. Like, "what year was yellowstone national park created" I didn't actually ask it, but I am confident Google would get the answer and I doubt Amazon would.

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.