larryllix

You would require a three wire cable a d the bare ground doesn't count. Dimmable receptacles are a bad idea and I doubt you will ever find one in upper North America. Sent from my SM-G781W using Tapatalk

Toe testing the water to bring the investment debt out of the devil's pit? Sent from my SM-G781W using Tapatalk

Oh sorry. I have never used the output contact statuses. I always did my own setpoints inside ISY with longer or shorter cycled the humidifier appropriately based on the ISY setpoint. However I did sync my ISY setpoints off my ecobee stat humidity setpoints. When I built my home many contractors stated I would never need a humidifier, based on the sealing of my construction, so I built the air handler space too tight to add one. Boy, were they wrong! If you use an HRV ventilation system in the winter climate. I used a large room humidifier and had to haul water regularly in winter months. 😪 IIRC, my ecobee 3, and ecobee 4, only ever had one extra contact output. You had to take your choice between usage setup.

yes. you can see them in the status page and use them in programs to read or set Sent from my SM-G781W using Tapatalk

Text messaging has changed over the last few years. They were never guaranteed as instantaneous and now can take days to arrive. This is very annoying as another good medium has been wrecked.

Usually providers provide a conversion address method to convert emails to SMS so you can use the native ISY notification action system. it usually looks something like 1234567890@verizon.txt.com do a search for listed domain names. Sent from my SM-G781W using Tapatalk

I always use the bash script via PuTTY to upgrade and always have to power cycle polisy complete. Something always hangs after until a complete reboot. Other upgrade methods have never worked for me and the bash commands are already embedded into the command line memory so I can access it with a few keystrokes. I have tried the online menu options, and the reset button method but had no success. Things may have changed in the last few upgrades though.

Most electronic devices have a circuit that keeps individual circuits from running or causes a general reset after power is fully restored to all circuits at functioning levels. With SmartHome's horrible reputation of cutting out components until the prototype won't run with even one less component, my opinion is that you are totally correct. I doubt any Insteon thermostat had enough "brains" to remember bad things from a poor power down sequence or cause a polite power up reset to ensure proper quiescent state. While voltage is quickly waning you don't have time to write cycle data to an EPROM memory.

Always factory reset before linking to ISY. Sent from my SM-G781W using Tapatalk

I had two of the 2441ZTH units and found those units were bad news. My oldest one worked fine but when I got a newer model ISY could not ever control it. The newer unit always reported status changes but after an online support call from Michel, he pointed out the stat was reporting changes sent by ISY as confirmed each time without actually changing anything in the stat. The newer stat had an actual engineering design defect built in. Of course they wanted me to pay for return shipping to get warranty repairs honoured. That was one of the 3 for 3 items they sent me in that order that turned out to be defective on arrival. Another item was the iRLinc with a reverse wired iR sensor. In each case the return shipping costs were higher than the devices were worth. I never ordered directly from SmartLabs again. I digress but to be short..I wouldn't trust Insteon stats to control my doghouse. Sent from my SM-G781W using Tapatalk

After a complete power outage, what difference would the slow death of the power supply be? I doubt an Insteon thermostat would remember how it died that a simple linking button would solve. If a factory reset was necessary, I could see that, possibly. Depending on your HVAC zoning configuration, 1 x ecobee stat with 9 remote sensors may do your job but then you would be faced with 9 x CR2032 batteries to replace every 2-3 years.

Thanks for the report. What type of sensor was it?

I have had an IP duplication a few times in my life. It isn't always the devices with duplicate addresses that act up. A few times the whole router network acts up and they can take turns at random or stay with the same device lockout. I had about 60 devices locked down in my last setup with IP reservations and when you get a duplicate due to some bootup error you can sweat for days trying to find it. The symptoms are way to random to zoom in and you can't get your system performing properly to diagnose it either. Sent from my SM-G781W using Tapatalk

That sounds like a recipe for disaster. Unless every device is manually IP address locked or you even have one dynamic IP address that your router can DHCP assign, sooner or later you may experience what looks just like what you have right now. I have been there a few times over the years and trouble is it can change every time you reboot or power cycle. BTW: I ran various models of ASUS routers and unless you power cycle them, some problems never clear up from a reboot. I have 2 x ax92u WiFi6 mesh routers for sale right now. Lots of features but as undetectable ad the last one I dumped. I hear reports that Ubiquiti are about the same calibre, from some sources. ***sigh*** Sent from my SM-G781W using Tapatalk

You will also likely need the latest version of ISY you want to install after a factory reset.

Power cycle your router. This sounds like you may have created a duplicate IP address, and power cycling your router may change some IP addresses around to allow you to connect with your ISY. This also sounds like you are not using DHCP in your ISY. This can cause IP confusion when two IP addresses clash. Always set static IP addresses inside your router so that it can manage them properly, avoiding IP address duplications.

Does that mean it is a switch or just a hub, repeating everything it hears? IOW: Is there any intelligence / arbitration between the three ports or do all ports get the same data?

Since all others use these interfaces with complete success, it suggests you have something not set quite right. What version of ISY are you running?

That one always puzzled me too. Possible they got an agreement before the change in management, or change of mind, inside Smarthome. If they could get access to the technology and sell it, why couldn't UDI ?

I never declare any devices as a "light" in my Alexa app. All items are defined as "Device/Switch" and they all control an ISY program. I only use On and Off commands. To do this, all programs control Insteon Scenes and program Scenes (mostly WiFi lighting) with various brightness levels. eg. Alexa.. Turn on dim lights Alexa...turn on bright lights Alexa...turn off all lights Alexa...turn on very dim lights Alexa...turn on red lights Alexa...turn red deck lights The only "All lights" defined is the ISY program I wrote. Alexa doesn't know I have any lights. Everything is just a device. I don't want Alexa trying to do any AI guessing crap. Having said that, Alexa will ask you about each and every device, at some time, whether it is connected to a light. Say "No"

Did you get the PIN installed into your ecobee account successfully?

if you are running windows, lower your screen magnification temporarily until you are done using the admin console. Admin console is based on some older monitor parameters that haven't progressed with the times, apparently. Sent from my SM-G781W using Tapatalk

I don't see Insteon joining Matter. From what I can decipher the protocol's lower OSI level (hardware) is only going to support 2.4GHz, 900MHz and 850Mhz. IMHO if you allow three different frequencies you may as well not spec any RF or hardware comm technique. You have already divided the industry support in three possible sections. **sigh**

I see matter as just another of the 10,000 protocol failures coming to complicate the market even further. I watched this happen with DNP 3.0 and several other 'universal protocol developments. Here is one of the problems....since none of the manufacturers can totally agree they will put manufacturer specific codes inside the protocol. This way manufacture X can support video while manufacture Y doesn't want video but needs control of bitcoin exchanges. Now we have a universal protocol that no brand will communicate with any other brand and the whole concept flops. The real answer is to get all the manufacturers to drop their own ideas and products and work together. Not going to happen ... but we will now have another protocol to divide the hobby up even further. Sent from my SM-G781W using Tapatalk

I looked at this a year ago or so and came to many conclusions, even with the mystery surrounding the sales hype being put out. It will mostly be using existing WiFi, once the standard is actually released and exists. Some have already built it into their 2.4GHz router APs. WiFi6 with mesh will the closest thing to describe it and likely be focused on for it's lower and hardware OSI layer. Many standards and industry co-operations will likely destroy it, due to no common hardware protocols in place when it is released in devices. Many HA companies will want to use the lower band frequencies for better building penetration, and that may defeat the whole "one for all, and all for one" concept they are attempting to sell it on. We'll see but IMHO we have been here many times before and all wee see is failing HA protocols, so far. Insteon has faired quite well until lately. Hope...hope...