stusviews

It's not just the thermostat. I've struggled with newly created programs nor running only to find success the following day. Glad it's working for you. Everything you did was correct

Just as a test, try Control instead of Status.

Not at all. Did you run the usual tests, e.g., run Then? Trying different setpoints?

What you listed are program triggers. You find what Larry suggested under program conditions.

I have a KPL button lit when the garage door is open. That requires that the sensor be wired to N.C. contacts from the magnetic sensor switch as oberkc suggested. Reverse that if you want the indicator to be lit when the garage door is closed. Do no use reverse sensor.

Add the device and the scene to Alexa. Give both a unique name that you won't ever use. Add the device to an Alexa group. Add the scene to the same Alexa group. Name the group a new desired name. Ask Alexa to turn on the new desired name. The device will turn on at the chosen scene level. Ask Alexa to set (or turn on) the new desired name to, say 80%. Voila!

Are you using the ISY to control the thermostat. If so, then what's the result if you adjust the thermostat manually or depend entirely on the Nest's ability to automatically control the AC?

Success, but not with the method you suggested which gave the same result. But, based on your implication, I made a copy, renamed the original program, gave the copy the original name and was able to add the "new" copy. I then deleted the original errant program. Thanks

I created two programs, GG3 Driveway Gate and GG4 Walkway Gate. I attempted to add them to the portal. GG3 added with no problem, GG4 appeared in red, indicating that it was already added when it was not. I tried adding a spoken, the portal indicated that the program already had a spoken. The program was nowhere in the list of named devices. I deleted the program and it did not appear in the portal list of programs. I re-created the program with the same result, the program shows red. Renaming the program gave the same result. The portal indicated that the program was already added (appeared in red), but it was not ever added. I got the same result when attempting to add the program to a different portal account (same portal, just a different account). Any suggestions?

Factory resetting everything will probably save you time in the long run. And get a whole house surge suppressor. which will save you both time and money in the long run.

The first two digits represent the year of the firmware, the second pair is the week. And yes, 2 years is the predicted lifespan, more or less. Keep in mind that this is only the reported failure. No one posts about older PLMs that haven't failed

After the PLM is successfully swapped, create a new backup. Restore the new backup to the new ISY.

Any Insteon device I've ever received from Amazon has been very current.

Nope. Swap the PLM. If everything is OK, then you're done (there'll be some minor fixes you'll have to handle manually such as restoring battery powered devices one at a time). If everything is a mess, then you'll need to restore from a known good backup made before the swap.

What's the result if you ping the given IP address?

Insteon does not have a lower/higher thermostat. All three thermostats are programmable. In fact, all three thermostats are identical except as follows: 2441TH: Wired, meant for conventional HVAC systems 2732-242: Wired, meant for heat pump systems 2441ZTH: Battery powered, meant to be used as an accessory for either wired Insteon thermostat. A wired thermostat can be controlled by up to two battery powered thermostats. The 2441ZTH cannot control an HVAC (or heat pump) system unless it's linked to a wired Insteon thermostat. Extra: if the 2441ZTH is NOT linked to a wired Insteon thermostat, then it can be used as a stand alone thermostat to control another Insteon device.

It's worth a try. You do need to include the lock by bringing it close to the ISY, then you can install it in its final location. An Aeotech Siren or Doorbell will work wonders to increase the range, if needed.

A known good backup should work. No purchased modules will transfer. You'll have to have ISY update those modules. You may want to create a new backup and install the new PLM first.

Agreed, the connected device matters!

Pairing a dimmer with an on/off switch is no problem at all. Both devices will behave as the one connected to the load. If the load is connected to the dimmer, then both devices will act as a dimmer, if the load is connected to the on/off device, then the dimmer will be an on/off device. So, Techman, you are correct. The connected load matters.

Info: Schlage Connect is a service, Schlage Connect lock type/name is a device. (e.g., Schlage Connect BE469 or simply Schlage BE469).

If you (easily) install the ISY Z-Wave module, the you won't need Schlage Connect which is a for a fee service to control Schlage Z-Wave locks. You'll be able to fully control the lock with the ISY.

Schlage Z-wave locks are my choice.

Yes, that's correct. One portal can accommodate four sub-accounts for a total of five accounts. You'll need an Amazon account (free) for each portal account. You can now mix Amazon and Google accounts. My main goal for multiple accounts is "natural" speech. When in the bedroom, for example, we ask Alexa the turn on the light. There's no need to say, "bedroom light." The same for the living room. We do need to name the room if the responder is not in the room we're in.

So is their Wiki. BTW, wiith 14 window covering, I decided I needed more than 16 channels. With the extra port on the Autelis interface you can add up to three additional Somfy interfaces (16 channels each). It's $10 if you order it at the same time, $35 if you add it later. You get one guess on how I know about the add it later price