PurdueGuy

To add to what @jfai said, I am using less and less times directly in program conditions. I have moved to having multiple programs that enable/disable other programs as needed. Then in the program, I have just the conditions (motion sensor status in your case). This way I don't have programs triggering at odd times.

Allowing the user to get the current IP address of the ISY on a (typically) closed network is nothing compared to: - disarming a security system - unlocking a lock - running a furnace Plus, the IP address is included in every single network connection the ISY makes (at least on the local LAN).

I don't see how divulging an IP address (most likely an internal and non-routable IP) would be much of a security concern. If you are on the network, you can easily see quite a bit of traffic.

You are also better off creating 1 scene with 4 responders. That way you can turn that scene off, and they all go off in unison, instead of one at a time in rapid succession ('popcorn effect').

Man, I leave for a week and big news hits! Congrats to @Michel Kohanim and the rest of the team! Way to go!

The quickest answer is, as far as I know, the on/off on the keypad are directly tied to the "load" output from the switch. They cannot be decoupled. As I am reading the OPs original post: Wiring: FanLinc input wired to Hot 2487S (KPL) input wired to HOT FanLinc: Light output wired to fan light. Motor output wired to fan motor. 2487S load (red) wired to secondary fan assembly that rotates fans. Desires: KPL On/Off BUTTONS control fan light via FanLinc KPL scene button (A/B/C/D) control fan motor via FanLinc KPL load (red) controls rotation assembly motor The short answer is: no, I don't think you can do this with 1 FanLinc and 1 2487S. The KPL On/Off button will always control the load. You can have the load go nowhere, but you can'y decouple them. It would be great if I am wrong though. I am guessing it is some setup like this. (In this example there is no secondary motor to spin the fans, but doing do would be easy. This example just spins them based on the fans moving air themselves.

Your first post was 13 hours ago and you've already given up as of 5 hours ago? So you gave them 8 hours to respond? With other products, I've waited weeks/a month for tickets to be responded to. UDI is typically quite willing to help, and almost always bends over backwards to help people out.

Check the "On Level" hasn't been set to 0? The "Restore Devices" should have reset it, but if the On Level was set to 0 and ISY things that's correct, it will put it to 0 when you restore. When you controlling things from the ISY, are you using a scene? The individual device?

Using Status it will trigger whenever the status reaches the proper value. But there is no Fast On for a status. If you are trigger from an app/AC/Alexa/etc, trigger the program (or trigger another program that calls this program). Or set a variable that will call this program. Since you are in the land of software triggers, there are a number of things you can do.

There is also a 3-plug version for $26. https://www.amazon.com/Kasa-Smart-Protector-Required-KP303-dp-B083JKSSR5/dp/B083JKSSR5

With an ISY in the system, you should always create scenes via ISY. Otherwise, the ISY won't know about the scene, and could overwrite it at some point. Also, creating them in ISY makes it very easy to change on level, ramp rates, etc. Creating via the Set button is more work. And some devices (FanLincs, etc) are annoying to get to the Set button.

It sounds like the modules and new PLM haven't been linked together. You followed these steps, correct? https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_.28PLM.29 Is it just those modules? When you turn on or off other devices, the ISY shows an immediate status update for that device? Maybe when you did the restore ISY could not communicate with those devices? You can try to right-click and Restore Device...

Also, depending on how many devices and which firmware version... For times you don't want them to react, if on v5+, you can set them to "ignore" (at least I think that started in v5).

Does regular Polisy have Bluetooth built-in? (I don't know if it's enabled yet. or will be.)

Hi Michel, I got the Weather Module notice, so I don't know which category that falls under. However, I try to select all 5 options, but after it saves, 2 of the options are shown as unchecked. Product News & Announcements Beta Firmware Announcements Thought you should know. (I do receive a confirmation email that my account was updated, so something is happening.)

I am well aware of what the OP wants, as I do the EXACT same thing with Alexa. Alexa talks to the fan directly, and a few seconds later the ISY "fixes up the KPLs" - it's the exact same scenario. It really depends on the scene definition. You've created 4 scenes, that the ISY tries to commit all 4 scenes (3 offs and 1 on) at once. Who knows if the KPL will be able to see all 4 commands and act on them. That's a lot of traffic occurring all at the same time. And if you use the KPL to initiate the change, you've now added even more Insteon traffic at the same instant. It's always best to have as few number of scenes as needed. You'd be better off doing what I have listed, and don't include the fan as a responder (but then you need more scenes total instead of just the 4 I have).

Do not put the "off" in the else. You might be causing a race condition in the ISY and messages clobbering each other. Have just 4 scenes (each with fan and all buttons set appropriately), and 4 programs, each with an "IF" and "Then" (no "Else"). I described my setup here, and it works well for me using Alexa.

Unfortunately that's the way AT&T does it. It used to work better if you used the AT&T MMS email address. Everything would come from the same number, but that stopped working a while ago. I'd recommend you looking into Pushover or something similar.

This is the program that sets all the on levels. $iHallwayOnLevel = On level $iHallway_RampRateIndex = the speed at which it gets to the on level Other programs set the variables, and then call the following program: Hallway Adjust - [ID 0098][Parent 0094] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then // Controller is ISY In 'Upstairs / Hallway' Set 'Upstairs / Hallway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index' In 'Upstairs / Hallway' Set 'Upstairs / Hallway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index' In 'Upstairs / Hallway' Set 'Upstairs / Stairway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index' In 'Upstairs / Hallway' Set 'Upstairs / Stairway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index' // Controller is Hallway In 'Upstairs / Hallway' Set 'Upstairs / Hallway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Hallway' Set 'Upstairs / Stairway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Hallway' Set 'Upstairs / Stairway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries // Controller is Hallway-Remote In 'Upstairs / Hallway-Remote' Set 'Upstairs / Hallway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Hallway-Remote' Set 'Upstairs / Stairway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Hallway-Remote' Set 'Upstairs / Stairway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries // Controller is Stairway In 'Upstairs / Stairway' Set 'Upstairs / Hallway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Stairway' Set 'Upstairs / Hallway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Stairway' Set 'Upstairs / Stairway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries // Controller is Stairway-Remote In 'Upstairs / Stairway-Remote' Set 'Upstairs / Hallway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Stairway-Remote' Set 'Upstairs / Hallway-Remote' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries In 'Upstairs / Stairway-Remote' Set 'Upstairs / Stairway' To '$iHallwayOnLevel %' in '$iHallway_RampRateIndex Index', No retries // Set Local On Levels & ramp rates Set 'Upstairs / Hallway' On Level '$iHallwayOnLevel %' Set 'Upstairs / Hallway-Remote' On Level '$iHallwayOnLevel %' Set 'Upstairs / Stairway' On Level '$iHallwayOnLevel %' Set 'Upstairs / Stairway-Remote' On Level '$iHallwayOnLevel %' Set 'Upstairs / Hallway' Ramp Rate '$iHallway_RampRateIndex Index' Set 'Upstairs / Hallway-Remote' Ramp Rate '$iHallway_RampRateIndex Index' Set 'Upstairs / Stairway' Ramp Rate '$iHallway_RampRateIndex Index' Set 'Upstairs / Stairway-Remote' Ramp Rate '$iHallway_RampRateIndex Index' Else - No Actions - (To add one, press 'Action') The values currently only set based on time of day. I haven't gotten around to redoing it based on light levels since the original Weather Module went away.

Just wait until you create just one scene, and use a variable to set the brightness levels depending on the use case. For example: I have an upstairs hallway, which includes: SwitchA (connected to 1st set of lights) SwitchB (connected to 2nd set of lights) SwitchC - 3way (no load) SwitchD - 3way (no load) So, when I want to change it from day mode (80%) to night mode (10%) there are a bunch of links to update. So I have a program that sets everything to a given variable. It makes it easy...just one program to update, and I can easily change the day mode percent based on cloud cover, etc.

Yes...just set the device level to Off/0%. I attached part of my "Away" scene. It shuts down the house, but leaves a path to the exits.

No. A scene just has devices. Sounds like comm problems, and commands from certain controllers can't reach all devices.

It depends on what you want to do. In a standard 3-way, where there is just one actual load, yes, you probably want to "turn on the scene" so that everything stays in sync. There is no "query a scene" and has been discussed hundreds of times. What would "scene status" mean to you? A scene is "on" if what? All the devices are on? Most of the devices are on? What is they are not set to the exact level of the scene? (One device is at 49%, instead of 50% as per the ISY-managed scene. Does that mean the scene is on? It's 99% on? It's 49% on? Everyone's definition would be different.) If you really want to know when a scene is on, watch for whatever triggers the scene to turn on. A "Control Switch is turned on" for either switch would do it. If a scene is triggered via a program, well you have the trigger already. You could also use device status, is there is just one device....and use ANDs if more? (but that gets cumbersome, and you're better off catching the trigger): Or "Status SwitchA is xxx%" Or "Status SwitchA is not Off" Something like that.

Looks like I am back in business! Alexa works, and my Polyglot heartbeats restarted! Thanks!

Also, Alex says "The hub that devices connects to is not responding..." Commands via Alexa (voice) worked about 20 minutes ago.