simplextech

There were talks/plans/ideas of a Zigbee module. I don't think it's available yet... but that's the idea. Having a z-wave or zigbee module and then having the external gateway to provide remote access and to interface with Alexa/Google voice assistants.

The Z-Wave is a module that fits inside the DB2 locks. The Wifi gateway is an external box that communicates to the locks via BlueTooth.

The Alfed lock when used with Z-Wave is local to the controller. When used only with the App it is cloud + Bluetooth for local control from your phone. When combined with the Wifi gateway you can use the mobile app remotely which is cloud based and the gateway connects local via Bluetooth to the lock.

Disclaimer: I do promote and discount the Alfred locks If going with a Z-Wave lock first you want to plan out and ensure you have enough powered devices for a strong mesh. Secondly I do like the Alfred locks and if you couple that with their Wifi bridge you get the best of access and control. The lock can integrate to the ISY via Z-Wave for all of the automation and control plus with the Wifi bridge you can use the mobile app for remote status/control and for configuring user codes.

Oh that's new to me. I'll have to give that a try!

To my knowledge only 1 ISY can be linked to Alexa/Google for voice control at a time from the same ISY Portal account.

Probably right. Time to install their own router + firewall for their own LAN to have control of stuff inside their condo and secure their network traffic then.

Why not add a DHCP reservation so the IP never changes? No guess work then.

that would be great.... if I had an Android device this would run on.

oh ok. If you have it set to 5,000 that should be high enough that it's not timing out the connection. But I don't know what the back end is doing. If it's intermittent in responses it might be a time out issue. I don't know if L3 in the event viewer shows network resource information??? Maybe?

I thought i saw the screenshot in your other post? It was 500ms

Play with the timeout settings in the Network Resources. Often it's that simple. Posting the MAC address is pretty harmless especially since I highly doubt your blinds have a direct internet connection

Z-Wave scene functionality with the ISY is handled via programs. I think I may have a Zen22 and maybe Zen21 around here in a box. If I get time I can validate the scene functions.

As already mentioned there's not fun/good way. You will have to exclude the Z-Wave devices from SmartThings before they can be added into any other controller. This is not specific to the ISY. @lilyoyo1provided the nuclear option of resetting the devices You can also exclude them one at a time in SmartThings and then Include them into the ISY. Either way there's no quick or fun way to migrate your controller.

Disclaimer. Port forwarding is BAD!!!!!! Did you reconfigure SSH to use a port other than 22? If not then it's still the default port of 22 for SSH.

If you're remote then you won't be able to SSH to the box unless you are port forwarding port 22 to the public internet or you have a VPN connection.

They can work locally in the same manner as the older units. I just installed 2 x new Chamberlain systems and I used an additional control unit for each that I mounted in the attic above them. This is just a normal button controller to open/close the doors but it has additional wires added for pulse input. I can control the doors through my Lutron VCRX just like any standard "dumb" door. The same could be done with IO Lincs or Z-Wave controllers or whatever you choose.

That's odd for them to fail at the same time. I've had them fail from time to time and like you I replaced them.

I did read through your saga. I don't use the MyQ mobile app "rules" so I don't know if this is a problem or not. I don't use the MyQ app for much of anything actually. Depending on what it is that you don't like about the I/O Linc you have option of using a Z-Wave relay controller as an alternative to the I/O Linc.....

I don't want to interject here...but I'm going to More z-wave devices (powered/plugin) is always a good thing to extend the mesh robustness. However you may want to decide on a final goal/direction of protocol first. Do you have Insteon switches already? If so you should think of keeping them for the Insteon network to be robust. Insteon lighting is much better than Z-Wave lighting. (IMHO). If you really don't want Insteon for lighting then skip Z-Wave and go Lutron. What's the goal or use case for Z-Wave? If it's sensors, locks, etc then plugin modules are ok but you might want to think about receptacles to build out a nice strong z-wave mesh that can't be unplugged by accident. Then use plug-in modules to extend or grow when you can't add receptacles. The receptacles (almost all) provide "beaming" which is a necessity for locks to function properly. Most plug-in units do NOT provide "beaming" so if locks are what you're looking to add you need to be aware of that. You can use plugin-in z-wave range extenders and they do support beaming and they can augment a z-wave mesh. Several things. Most importantly is a stronger signal and what's referred to as "instant status" or the simple thing of a device telling the controller when it's manually turned on/off so you don't have to query the device to get accurate information. Useful for programs. There's a lot of benefits to Z-Wave Plus so if you're starting fresh with Z-Wave and going to be adding new devices just bite the bullet and upgrade to the Z-Wave 500 series board now and only buy Z-Wave Plus devices. I do Z-Wave device testing and add to this list when I test something new. If there's some device you're interested in but not on the list I may be able to get one for testing. https://github.com/UniversalDevicesInc/Z-Wave-Devices/issues You can also add to this list if you want.

"Best" is always subjective. A list of various priced units that can work with Blue Iris that I'm aware of DoorBird GrandStream 2N Amcrest Video Doorbell Camera (not tested but they claim RTSP support) very cheap option too.

Why not use a Thermostat that works with 240v electric heating?

Please add it to the list along with notes. https://github.com/UniversalDevicesInc/Z-Wave-Devices/issues

If the point it to have motion detector in the ISY trigger an event in Homeseer why not use the ISYInsteon plugin for HomeSeer? Then it's local and no Alexa/Cloud involved. Set variable triggers in Alexa.. check Alexa routine passes to HS...check ISY sets motion variable.. fail. Looks likes your program to set the variable isn't working correctly?

LIP -> Lutron Integration Protocol is ascii. It's literally a socket connection to the ascii interface and you can access and read/send commands with any telnet client. So yeah it's unlocked Some out there will throw stones because it's "unsecure".... well it's ascii numerical data and it's just lights Sample output from a running nodeserver in development: Output a main repeater: ~OUTPUT,40,29,11 You tell me what that is Caseta Pro, RA2 Select are both "programmed" from a mobile app. There isn't any programming. You can create scenes/groups of lights and some basic actions. You will have to use a control system to do anything really fancy with them. There are no keypads for Caseta or RA2 select either. They are "entry-level". The upside to RA2 Select are the dimmers/switches are compatible with RadioRA 2 so all you have to replace is the Main Repeater. With Caseta the only thing compatible between the bigger brothers are the Pico remotes. I'm bringing @lilyoyo1comments in because they are also important. If you want a fully/tightly integrated system with rock solid reliability then go with a C4 or Crestron as they each have their OWN lighting controls and most other components as well. Tightly integrated single vendor solution. You won't get to tinker as much but it is rock solid if you get a good programmer to setup everything. This is also a valid point to consider. When working with multiple systems and integrating them there's higher probability of problems. As it stands currently the RadioRA 2 nodeserver is still in development and not released as of yet. I expect as is normal that there will be some issues that come up which aren't caught in the testing. They'll get fixed quickly but nothing is ever 100% reliable 100% of the time when humans are involved somewhere in the mix.