jec6613

You can take the courses to get access to the RA3 software yourself, much like RA2Select. RadioRA3 requires cloud for the app, but the API is local for automation systems with no cloud dependency. RadioRA2 is commonly used with the likes of Crestron and Elan with full offline control (Caseta is too, for that matter). Provided you're not using the Lutron app for your schedules and primary UI, you'd never know if the cloud went fully offline.

There's also a Caseta node server, so you can use Lutron Caseta. Depending on your timeframe, Lutron Sunnata and Lutron Maestro (via RadioRA3/RadioRA2) are also a possibility. The Maestro are the closest to Insteon I've been able to find in terms of how they function, with Maestro having a better dimmer and more luxurious feel (except for the button click for some reason).

I have no trouble with my T6 Pro like you're describing, either with the ISY994iZW Pro or the ISY on Polisy. Queries work fine, and since it's configured properly for my HVAC system, I don't have any short cycle or long delay issues. Of note, however, if it's not configured with the correct CPH and other settings (and there are ~100-ish on this thermostat) I would expect to have odd behavior. Out of the box with all default settings, I will indeed have quite poor thermostat behavior for both comfort cycle delays.

Lutron is different, and has a few product lines, from their training: Caseta: up to 75 devices and 1 repeater, 400 MHz RA2Select: Up to 100 devices and a pair of repeaters, 400 MHz RadioRA2: Up to 100 devices and a pair of repeaters (dealer only), 400 MHz RadioRA3: Newest, up to 100 devices on 2.4 GHz + 100 RadioRA2 400 MHz devices and every device with a neutral wire is a repeater QS: up to 10,000+ devices (I'm not familiar with it) If you want more info, please take their trainings - most of them are free for at least the basic product info, and go into a good amount of detail without being over-involved. For a quick list of pros/cons: Lutron does lighting and HVAC only, Z-Wave as a myriad of oddball devices like door locks and mouse traps. Lutron is a single vendor, if you don't like their aesthetics or assortment than you're SOL. Lutron's lighting system is just plain better. It's the only competitor to Insteon that avoids popcorning, and it's extremely reliable when installed correctly. Z-Wave is significantly less expensive. Z-Wave has longer reach if you have a strong mesh than all but RadioRA3 or QS systems. For my money, when I switch off of Insteon in the future, my lighting will go Lutron and my other devices Z-Wave.

Odd to me that if it doesn't include a power supply, it doesn't have a DIN rail option at least. Would make total sense in a big DIN enclosure.

To my knowledge Lutron does not make any Z-Wave devices, they have their own proprietary RF technology that offers functionality on par with Insteon (e.g. no popcorning and so on), though the tech is very different under the hood. Could you be confusing Lutron with Leviton? Leviton does indeed make a very large variety of Z-Wave and WiFi devices.

For lighting systems, Lutron's are the best replacement (Z-Wave is still way behind). For everything else, Z-Wave is where it's at.

First, this is what I get when I put in the configuration information. I've sanitized MAC and IP, obviously 022-04-21 14:11:30,003 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.40 Starting... 2022-04-21 14:11:30,255 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.0.56 [ISY: 5.3.0, Slot: 4] 2022-04-21 14:11:30,257 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.xx.xx', 'netmask': '255.255.255.0', 'broadcast': '192.168.20.255'} 2022-04-21 14:11:30,259 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-04-21 14:11:30,268 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-04-21 14:11:30,269 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '3.1.6'}} 2022-04-21 14:11:30,316 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-04-21 14:11:30,318 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:52:bf:7c_4 - MID: 1 Result: 0 2022-04-21 14:11:30,334 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-04-21 14:11:33,284 MainThread udi_interface.interface INFO interface:addNode: Adding node DysonFan(controller) [None] 2022-04-21 14:11:34,918 Thread-4 udi_interface ERROR dysonfan:dysonConnect: Error connecting to 192.168.xx.xx, 'NoneType' object has no attribute 'connect' 2022-04-21 14:11:34,920 Thread-4 udi_interface ERROR udi_interface:write: Exception in thread 2022-04-21 14:11:34,921 Thread-4 udi_interface ERROR udi_interface:write: Thread-4 2022-04-21 14:11:34,921 Thread-4 udi_interface ERROR udi_interface:write: : 2022-04-21 14:11:34,922 Thread-4 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-04-21 14:11:34,923 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-04-21 14:11:34,927 Thread-4 udi_interface ERROR udi_interface:write: self.run() 2022-04-21 14:11:34,928 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-04-21 14:11:34,932 Thread-4 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-04-21 14:11:34,933 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:7c_4/nodes/dysonfan.py", line 71, in start 2022-04-21 14:11:34,934 Thread-4 udi_interface ERROR udi_interface:write: self.dysonConnect() 2022-04-21 14:11:34,935 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/xx:xx:xx:xx:xx:xx_4/nodes/dysonfan.py", line 98, in dysonConnect 2022-04-21 14:11:34,936 Thread-4 udi_interface ERROR udi_interface:write: LOGGER.debug(f"Auto Mode is {self.dysonData.auto_mode}, Night Mode is {self.dysonData.night_mode}") 2022-04-21 14:11:34,937 Thread-4 udi_interface ERROR udi_interface:write: AttributeError 2022-04-21 14:11:34,938 Thread-4 udi_interface ERROR udi_interface:write: : 2022-04-21 14:11:34,938 Thread-4 udi_interface ERROR udi_interface:write: 'NoneType' object has no attribute 'auto_mode' 2022-04-21 14:11:57,798 Thread-5 udi_interface ERROR dysonfan:dysonConnect: Error connecting to 192.168.xx.xx, 'NoneType' object has no attribute 'connect' 2022-04-21 14:11:57,800 Thread-5 udi_interface ERROR udi_interface:write: Exception in thread 2022-04-21 14:11:57,801 Thread-5 udi_interface ERROR udi_interface:write: Thread-5 2022-04-21 14:11:57,801 Thread-5 udi_interface ERROR udi_interface:write: : 2022-04-21 14:11:57,802 Thread-5 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-04-21 14:11:57,803 Thread-5 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/xx:xx:xx:xx:xx:xx_4/nodes/dysonfan.py", line 106, in poll 2022-04-21 14:11:57,805 Thread-5 udi_interface ERROR udi_interface:write: if self.dysonData.is_connected is False: 2022-04-21 14:11:57,806 Thread-5 udi_interface ERROR udi_interface:write: AttributeError 2022-04-21 14:11:57,806 Thread-5 udi_interface ERROR udi_interface:write: : 2022-04-21 14:11:57,807 Thread-5 udi_interface ERROR udi_interface:write: 'NoneType' object has no attribute 'is_connected' 2022-04-21 14:11:57,808 Thread-5 udi_interface ERROR udi_interface:write: During handling of the above exception, another exception occurred: 2022-04-21 14:11:57,808 Thread-5 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-04-21 14:11:57,809 Thread-5 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner 2022-04-21 14:11:57,813 Thread-5 udi_interface ERROR udi_interface:write: self.run() 2022-04-21 14:11:57,814 Thread-5 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.8/threading.py", line 870, in run 2022-04-21 14:11:57,818 Thread-5 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-04-21 14:11:57,819 Thread-5 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/xx:xx:xx:xx:xx:xx_4/nodes/dysonfan.py", line 113, in poll 2022-04-21 14:11:57,821 Thread-5 udi_interface ERROR udi_interface:write: self.dysonConnect() 2022-04-21 14:11:57,822 Thread-5 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/xx:xx:xx:xx:xx:xx_4/nodes/dysonfan.py", line 98, in dysonConnect 2022-04-21 14:11:57,824 Thread-5 udi_interface ERROR udi_interface:write: LOGGER.debug(f"Auto Mode is {self.dysonData.auto_mode}, Night Mode is {self.dysonData.night_mode}") 2022-04-21 14:11:57,825 Thread-5 udi_interface ERROR udi_interface:write: AttributeError 2022-04-21 14:11:57,825 Thread-5 udi_interface ERROR udi_interface:write: : 2022-04-21 14:11:57,826 Thread-5 udi_interface ERROR udi_interface:write: 'NoneType' object has no attribute 'auto_mode' Second question, how can I put in multiple Dyson devices?

Exactly this. For something to go hard-off, it must have either: 1) A return path for current via a neutral wire, or 2) be powered by an external power source (this is how Z-Wave valve closers work).

I didn't say pause, just queue. Writing out to a device is likely less important than accepting new alarms, and this behavior was in the ISY994 as well.

3. Much more reliable integration into the PG2/PG3 on Polisy. But holy cow is it much faster. Nighttime automations that would take 20 minutes during which automations could lag up to 30 seconds, are now done in 5 minutes and no commands lag in the meantime. I have ~700 nodes, so that may be part of my issue, but still.

Because said nodeservers won't respond while you're doing the add/remove, I'd hazard a guess. The ISY has a good queuing system, and I'd rather it not miss a potentially important notification.

Outlook.com is way more secure than you think it is. Since the ISY doesn't support modern auth (modern auth = a specific Microsoft term referencing a method of securely connecting to a service using cryptographic tokens rather than passwords), you'll need to jump through some slightly unusual hoops to get it set up. Anyway, long story short: you need to update your SMTP server info: https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040 And you need to set up an app password: https://support.microsoft.com/en-us/account-billing/using-app-passwords-with-apps-that-don-t-support-two-step-verification-5896ed9b-4263-e681-128a-a6f2979a7944

I also have a small pile of Insteon outdoor modules, they work flawlessly. Regular old GFCI protected outlet, plug the outdoor module into it and pass the cord through the weatherproof in use outlet cover (which you have, right? There's definitely something where if an Insteon switch has heavy moisture exposure, it will start tripping a GFCI. It was a giant pain for me to learn to not mix a moist environment, GFCI, and an Insteon paddle, toggle, or outlet. For me at least though, it would not trip an AFCI/GFCI breaker, so I just installed that and protected the whole circuit and forgot about it.

Speaking of transitioning, is there a good way to send variables from an ISY994 to the ISY on a Polisy or vis versa, so they're in sync? Since virtually my entire house state is variable driven, being able to bring them over would let me slowly transition programs and devices in a good way over time, rather than having to just spend a weekend and bring everything over.

The way I handle old devices is I disable them, name them back to something generic (e.g. "Outdoor On/Off Spare #1), then stuff them in a folder called ~Disabled. And then they go into a box for storage. They're still in the ISY, and I can tell at a glance if I have spares.

I'd skip the percentage, and just have it stay off for 45 minutes, run for 15 minutes, off for 45, then repeat infinitely. Set the condition to trigger if bath-fan-switch is off (status, not control) Once the switch isn't off, the program stops. For your first program, remember to have it trigger with the bath fan switch is turned on, but when you turn it off to turn off the *scene*, otherwise the HRV will stay on afterwards.

I don't believe that will work, as the micro module looks for line voltage, so unless your photocell is closing a line voltage relay, you'll have trouble. An iolinc, on the other hand, would be a better bet with low voltage outputs. Both require that the output be binary though, they won't work with a voltage threshold. Of course, you could just use something like a Z-Wave or Insteon motion sensor that will give you light values. That's how I trigger based on light, just read the photocell output if I want fine-grained control, or use the dark/not dark node if they have one.

Yeah, my Z-Wave mesh exists just for my locks and HVAC. Though despite being 30 feet away through a staircase and such, the thermostat gets great signal to the ISY. It's the pro/integrator version though, the consumer one has lesser antennas.

I took the deep dive on this and went with a Honeywell Z-Wave. A few too many service outages on Ecobee and Nest that took out heating completely, and, really, what benefit do they bring? The ISY knows home, away, and room occupancy status already, so I'd skip the cloud bits and just get something reliable.

These locks are picky .. I ended up getting a bunch of Dome extenders as one of the few extenders they play nice with.

I perfer a temperature != $variable to a less than, but it gets to the same place. It means the variable isn't constantly stored to the same value if the temperature didn't change, so last updated time becomes meaningful for other uses.

I am also seeing this exact issue on three multisensors ... one secure and two non. Edit: Update, they now work after an ISY reboot. Not sure what was going on there.

I use the Honeywell T6 - the T5 is more readily available though. Both are very good Z-Wave thermostats that just work.

Their extender 6 is a 500 series device. They're fine, but the Dome are cheaper for the same thing so.... I think I ordered some of the last right now, shipments from China are way down due to lack of shipping capacity coupled with the stimulus checks driving Q4 type purchasing in electronics.