larryllix

Don't use scenes for it then. Use the devices. I don't use any scenes with the Echo, only programs that activate scenes for Insteon and dozens of other devices that co-oribate by programs only. "Alexa. Turn on xxx lights to 50%"

WE are using Echo more and more with ISY994 and alone, just web support. But we have found Alexa is almost completely useless in a crowded room with background noise and talking. You have to stand right in front of Alexa and speak loudly to get it to respond even about 50% of the time. The wall switches are just as easy then and always reliable.

LOL. OK. I thought we were discussing the KPL. I never use toggle mode on my KPL or mini-remotes and they function exactly the same except for the linking mode in the KPL, that never gets used with ISY.

In response to the OP post #6 "Push on/Push off control. Without having to press twice if the device is controlled by something else, such as schedule, other control, etc." You replied in post #7 "But if the remote truned it on it will remember it is on so if something else turns it off, the remote will think it is still on and issue an off command on the first push." The problem is the KPL toggle mode being used, and using only scenes does not allow a solution to that problem..

You and the OP already agreed in posts 6,7,8 & 9 that this doesn't work. Secondary buttons take no commands and do not understand other devices status. The LEDs do, but not the buttons.

KPL buttons do not know what state the device is in. The LED can if you control it from a scene showing the device is on or off but the button toggle sends On-Off-On-Off-On no matter what state the device is in. The only way to insure it only results (not sends) in a single push toggle is to turn the KPL toggle off, turn on the non-toggle On mode, and use a program to operate the device. The toggle function must be done inside ISY with the program dependent on the status of the device. Scenes cannot do this or help the button to know what state the device is in. The LED yes, but not the button command signal issued.

Without any experience doing this myself, IIRC you can't switch masters from ISY programs.

Did you power cycle your ISY after the purchase? Some things don't show up until reboot when they enable that feature/module. The Network Resource Module is existing in most versions of ISY firmware and just gets cloud enabled. I assume you have browsed your tabs to find it? It was an option to include it with the Portal Purchase. I didn't as I had the NR before.

What do you have updating the DDNS service?

The name shown in your device tree is for your Insteon network, not Ethernet network. Unrelated.

hmmmmm... My ISYfinder comes up with two IP addresses ( that I installed) and I have to double click one, to connect to ISY with the path I choose, every time. The local IP address and the remote IP address are easy to identify by their numbers and could identify two different ISYs also. There is no ISY friendly name used, or seen, there. Using MobiLinc Pro (android) the switching is done automatically dependent on whether your WiFi is enabled or not. Two different ISYs could be made to respond to LAN and WAN access methods. I guess I don't understand where you ever see a friendly name for your local ISY.

So you are manually switching the ISY IP addresses in your apps, to access each ISY and it's a PITA?

In the end you will probably end up writing an occupancy program using a variable to keep track if anybody is home or not. I have any Insteon action to trigger a "Home" varible and it times off with different stimuli. Like 20 minutes after I leave by my usual door. Immediately if I set the alarm system 4 hours if I trigger any other MS in the house. Never after bedtime until 7:00 AM again then 4 hours After creating this variable programs can use the variable to test for people home. If the variable is a state variable it can also trigger programs to run by itself or with other logic combined. Now you stop you furnace fan from cycling, ventilation off, temperature down or up, lock the doors after X minutes.etc..etc..

I am sure of one finger you are holding up.

That's probably the best method for 240v dryers I have heard yet. No electrical connections into the appliance. Gas dryers could be a problem using plastic in the vent line (probably not to code) but they are usually 120 vac and a SynchroLinc (as in my case) does it very simply.

IIRC, Safe mode is when ISY cannot find your PLM. You could try power cycling your PLM and then power cycling your ISY. Also check your PLM cable. It may be time for a new PLM or a rebuild but they usually don't go dead immediately, that I have heard here.

I use a variable in v5.0.4 to keep the date in format MM.DD This takes a separate program, but other programs can then use the $sMM.DD to test for date ranges, year independant.

v5.0.5 didn't solve the 2411T refusal to install. I didn't figure it was on the board for UDI, with the lump jumping they have been doing lately. Hopefully it will have a fix for all those that bought them during the SH iR Sending unit sale, recently.

Since you guys want to play with words again... Power doesn't go through a conductor. Power is consumed by conductors. Only current can go through a conductor. OTOH: In the context of a grid delivery system we do say "power goes through a conductor" (They sure do demand your ticket on a train!) Resistance is futile. You two will be assimilated.

The new iR sender module I just recived shows v0.4A formware in it. ISY can see it, read it's ID but refuses to connect with a "failed to connect" each time. I tried a dual band piggy-backed on it but the same results. It seesm to be communicating OK and ISY has the device listed in the pulldown but I suspect a new protocol that isn't supported by v5.0.4...maybe? IIRC Rast...reported a similar problem with his.

You need v5.0.x to do this or keep track of the current state via a central program that is the only one to operate the device. Some have used Network resources to feedback into the RET interface, effectively stuffing the level into a variable. Network resource --> Var substitution --> ethernet --> ISY Rest interface --> variable

I see nothing!

+3 "Hey Hal" "Hey b..."

One word that should be mentioned is . . . "Again" Which repeats the last thing you just asked for. My 6 y.o. granddaughter discovered that one with her constant gilrls music samples. grrrr..... She's getting her own Dot for Christmas.

That would be more natural for me and my cultural grouping. That covers from Colorado to Ontario. That's half the world.