brians

Roomie remote looks like it’s primarily a media av control remote software and they just added on some other abilities over time like home automation control. They don’t even seem to support home assistant which is very popular. From reading your posts I see you are trying ecobee, hue, and myq. All these support native homekit (myq with HomeKit adapter or hoobs) so what is issue with these and roomie, since you say HomeKit devices automatically appear in roomie? Is there some reason you need to have everything go through eisy for roomie remote?

Hue version of Zigbee on their bulbs is compatible with pretty much all Zigbee coordinators... it is their hub that doesn't work with other Zigbee devices. I run several Hue on my Home Assistant direct to my Sonoff USB Zigbee coordinator using Zigbee2MQTT (ZHA also works). Advantage of Hub is you can use the Hue app and make fancier scenes and stuff... newer Hue bulbs support bluetooth but I don't think has advanced features in the app, and probably limitation of range. I don't use Hue Hub, I just want to change lights different colours and have option to add different devices... there are much cheaper bulbs which are not so bad -I also have like Sengled zigbee about 1/3 the cost. LIFX are WiFi and I don't recommend, but I have a few older ones of those that I use still. The issue people will have with pairing a Zigbee RGB bulb to IoX with ZMatter via Zigbee/Matter is how to change colors easily? Does UD Mobile support color picker/wheel?

Re: #3 Secure devices will still route through non-secure devices/nodes. You just lose basic association between different security types... but most don't use that anyways since it is a bit more difficult to setup. Basic association was finally supported in ZMatter version of Z-Wave on IoX and makes the devices control each other directly. It is significantly faster vs.central scene method due to IoX's slower handling of events.

Zen17 works great and very reliable. All my iolincs died over time so would never buy another one again again. I’m moving away from insteon anyways and only devices that interest me are i3.

I use a pfSense router with Acme Certificates (letsencrypt), and HAProxy. I use to access things like Home Assistant, OpenSprinkler remotely, but can also be used locally with the FQDN... also setup Dynamic DNS via GoDaddy. I never had issue connecting to local IP address of PG3, but I rarely do and do not see a reason why I would need to connect to it often anyways - it's sort of set and forget and not really much to look at in there. Are these errors you are getting preventing you from accessing the site, or is it just an insecure site warning that you can click through?

Migrate to ZMatter is only applicable if you were using the older ZWave like the 500 series in ISY994i, or the Zooz 700 series USB in Polisy. If you already migrated to ZMatter from ISY994i then there is no need to migrate it again if you ever move to an EISY. Just make sure you have a ZWave backup.

UDI used to sell (or maybe still does) an ISY994iZ that had zigbee. This was used primarily for Energy monitoring and not for general Zigbee use. That link you posted is probably that version. Also there was this... https://www.universal-devices.com/product/smart-meter-module-sep-1-1/ You would have to contact UDI to see if they plan to support this with EISY.

I think you backup the ZWave dongle prior to making a full IoX backup on Polisy, then it becomes included in the backup. Upon IoX restore on EISY, you then restore the ZWave dongle.

ZMatter dongle appears to come with Zigbee hardware support, which is why the word Zigbee is silk-screened on it. Thread, for most part, uses same hardware as Zigbee but needs a firmware upgrade to support the protocol. If the device can do multiprotocol, it will be able to support both Zigbee and Thread simultaneously. Thread is just a protocol which Matter can work over and is ipv6 based, it is not Matter in itself. Matter is not a radio protocol, but it can currently run over Thread and Ethernet/WiFi which are both radio protocols. It is my understanding that you could theoretically run Matter devices as long as you have a thread border router somewhere in your network (eg. Homepod Mini), and the controller just uses ethernet.

@Bob AmottIs the light in ceiling fan dimmable? The Insteon Fanlinc light control is for dimmers. Your need to use fast on/fast off means that it sets the light to 100%, which seems to be needed to turn your lights on/off. I bet that is the problem and they won't turn on <100%.

That is my opinion not UDI's, so they could still support Zigbee and I hope they do especially since they advertise it... I would clarify with them first, maybe they will actually answer... I had posted this question a while back and got no official answer, just speculation from other members. I also remember them saying they would probably support Zigbee radio first and Matter would come later. Every other major hub seems to have no issue supporting Zigbee and then adding Matter later on, so the only reason I can think is because IoX never had Zigbee support, so is probably just as much work adding Zigbee as Thread (Matter). Based on lack of news and updates on Matter and Zigbee, it is a bit concerning how quiet they are on this subject. Maybe they are hard at work on it and will just announce one day. This is one (of several) reasons why I moved over to HA, but still keep Polisy as an Insteon bridge.

Good that you got working. It appears has something to do with s2 auth and scanning QR code should be same as entering the pin in AC. This is strange really but glad you have working.

@PatPendYes Zigbee is nice, but issue is that since it is an open standard and does not require licensing you will find compatibility issues. For example, in Home Assistant and Zigbee2MQTT, my Aqara P1 motion sensors go unresponsive after several hours when connected to a Sonoff S31 Lite plug. Nothing I can do except return them and try something else. I did add a couple Philips Hue bulbs and work quite well. Both networks in my house perform equally well but I only have 4 zigbee devices hooked up, whereas I have 22 ZWave devices. Pairing is about the same, except with S2 auth need to type in a code. I don't think we will see Zigbee support from UDI. Too many legacy devices to support, but never know. I think their plan is to support Thread (Matter) exclusively. It is not even known if the radio in ZMatter will support multiprotocol both Thread and Zigbee at same time. ZWave is a much stricter standard, and requires certification before can be sold as a ZWave device, and even still there are many issues. Zigbee is like the wild-west, anyone can make something called Zigbee.

Here is link to where I got it working back in 5.5.6 but this is a momentary sensor not garage. Since then I used one on Garage but I do not have a screenshot of it. However, here is documentation I made how to do for future: For Garage Door with ZMatter --------------- Connected the button and the sensor to separate sensor/relays just in case the isolation is not set correctly - if Zen17 is accidentally factory reset. Sensor is on S1, Button is on R2. Note with this config, parameter 2/3 can be set to 3 since there is no isolation required. However setting 2/3 to 11 isolates the relays and could use another input S2 for something in future. Reset Include in ISY (can be S0, don't need auth just to set parameter 2/3) Set parameter 2 and 3 to 11 for garage door (momentary mode) Set Parameter 2 to 11 Set Parameter 3 to 11 Exclude Include (use S2 Auth and key when re-including) This will add additional nodes Door-Window Sensors in addition to Binary Switches. Set Parameter 10 to 0 Set Parameter 11 to 0 This isolates the relays being triggered from the inputs Here is old info prior to ZMatter: NOTE: for Garage, following not needed if using parameter 2/3 to 11 which is garage door momentary. Type 11 was added in firmware update which makes garage door momentary with separate sensor nodes. I just left here for reference. To set simulate momentary 1 second Parameter 8: auto turn-off timer for Relay 2 Parameter 17: auto turn-off timer unit for Relay 2 Set Parameter 17 to 1 (seconds) Set Paramter 8 to 1 (1 second) *** must use 4 byte to write Parameter 20: Reverse the reported values for your selected input on S2 C terminals (select same value as parameter 3 eg. 7) (not reversed set to 0) Closed on Sensor 1 will show door closed Set Parameter 20 to 7 if your door sensor switch is NO (normally open) when closed.

Actually I think I remember that the Zen17 didn't label the nodes correctly like was on the old ZWave platform (not ZMatter). I remember I had for my garage door an actual sensor that said open/close and some Door-Window Sensor but with ZMatter I think the only useful thing was on/off. Is that what you are referring to? Here is screenshot in my current HA, but It showed something similar node when I used Zooz dongle and correctly showed an Open/Close Door node. With ZMatter this did not work. You will have to make do with the on/off node.

Are you including with s2 auth ?

Reinterview it after changing 10 and 11

Zigbee is not same as zwave. Zmatter board does not currently support zigbee.

Yes, I think the solution a bunch of us came up with before was to make sure you have the most current firmware on Zen17 then it works. The Garage door mode works in that it makes the switch momentary and shuts off after a second or so. The difference is that setting par2/3 to 11 it isolates the sensors from the relays. You don't need to set Par 6,8, 10,11, 15, 17 etc. to turn the relay off yourself... just need par 2/3 to 7 or 11. I had working exactly like this, and in fact just excluded from IoX to move over to Home Assstant.

Upgraded mine to 5.6.0 no issues. Had to restart PG3 in web interface, not sure why that cannot be done automatically as part of the upgrade. No issues, did not do the PG3x conversion prior because did not know anything about it (and am glad I didn't ).

OTA is hit and miss on other platforms too... eg. with Home Assistant it is not reliable so best to use a PC. Note that with IoX you have to change all automations/programs after excluding/including because the way IoX uses node ID's to reference in programs etc.

I think question is asking if IoX with Matter support will act like a Matter bridge and present all devices to the matter network. Then homekit may be able to see these as matter devices and supported in homekit. I think matter bridges are meant more as a way for end device manufacturers so they don’t have to add Matter support to each individual device eg Philips hue. However it is possible this may be case with IoX still and bridge devices.

Just use Home Assistant with ISY and HomeKit integration, it works great... probably better than if they had native support because of Apple's restrictions... https://community.hubitat.com/t/locks/107493 I just updated all my devices (iOS/iPadOS 16.4, MacOS, TVOS 16.4, Apple Watch), and works fine with the new HomeKit Architecture.

They should use ZFS and snapshot before each upgrade, if something goes wrong then can easily revert back. Since this is in EISY forum, what about Polisy also?

I also have similar issue, many Insteon switches with more settings cannot see all the settings using my MacBook Pro screen. Here is example of a regular size window in Win11 and cannot see everything at bottom, I have to maximize to 1920x1080 screen to be able to see it all... I see no reason why they cannot use multiple rows, there is lots of wasted vertical space not being used.