oberkc

As far as I can tell, my router is still using IPv4 addresses (192.168.0.xxx). The does not seem to affect my google nest and echo hub from being able to connect to matter devices (but these devices seem to loose connection to the hub and nest after some time). I think I have the IPv6 option selected on the router (netgear orbi) but I may not have enough knowledge to determine whether there are other addresses, public, private, or otherwise.

I have tried scanning two different devices (Nanoleaf bulb and Cync bulb) both factory fresh and after added to matter hub (google home android version generates QR codes to share). No success so far. I have also read somewhere that there is a relationship to matter and IPv6 network addresses. Not sure how this all works together or whether this is even relevant.

Not here. Trying Nanoleaf bulb (thread) and GE bulb (wifi matter). No luck so far. As far as I can figure out so far, the only way to add a matter device to the ISY is through UD mobile. And the only way to add through UDMobile is via QR code. So far, I have had no success scanning any QR code with UD Mobile (error "could not get matter QR code rendezvous Type: 500"). I have tried QR codes that came with the devices, as well as QR codes generated by nest home app on android (iOS version does not seem to have the ability to generate QR codes for attached matter devices.). UD mobile, as near as I can tell so far, does not provide the ability to manually enter the code and only allows scanning QR codes.

Don't get too impatient. Even on Android, the only matter capability appears to be cosmetic: menu items that now make mention of matter. I have yet to be able to actually "add matter devices". Neither have I seen any indication here that anyone else has been successful. Hopefully, I am just missing something.

On another thread someone had said that the iOS version is now available.

Did you download the new version of UDMobile? Don't disagree

I second that motion. The only message I need to see is the "failed writing...." There is a communication problem of some type. What devices do you have that are plugged into the same outlet and circuit as the PLM? Do you have any UPS or electronic gadgets/power supplies? Do you use any filterlincs? If you get a long extension cord and plug the plm into another outlet on a different circuit, does this solve the problem?

I cannot be much help with log files. I would be tempted to restore individual devices. Specifically, any of the devices that are misbehaving or part of a scene that is misbehaving. It may (or may not) help, but it is at least a simple step that could.

There is an update to the Android UDMobile app that one must download. As of yesterday, I don't think the iOS app has been updated (but soon, apparently). I don't see any options to connect with thread routers. The new app has a matter option now, as does the Admin Console. They only claimed that they had "laid the groundwork" for moving away from the Java interface If (when) you get the updated UDMobile app (and configure your IoX settings for matter), you will see an option to add matter devices from a barcode. I suspect this is for matter wifi devices. Not sure if it works. Not sure about thread devices.

My complaints of matter are much broader than UDI. Problems with matter seems to be a global issue. My only problem so far (very limited exploration so far) with the matter support in UD is being unable to figure out how to access any device through a border router (one of the claimed enhancements).

I just noticed the new app version for android. The version that I use on iPads does not have an update showing available. On android, I did not immediately get the option to add a matter device but found that there is something under settings regarding matter that led to rebooting my Polisy. We will see if this does anything. The whole matter thing, for me, has been a disappointment. I have been able to add a matter (thread) device to an echo hub and share it with a google hub, but this device seems to disconnect from the echo after a few days. I have not figured out how to share border routers so far. I find the whole thing underwhelming. We will see what the ISY update give us, if anything.

Upgraded here. It took not much time, probably less than 20 minutes. All appears well, but I have not tried anything other than logging in and noting that the Admin console looks normal. (I don't see anything related to matter other than the ability to enable it under the configuration tab). Now...time to see if I can figure things out.

I believe one needs to be on the same network to use the Java interface to IoX. That question strikes me as apples and oranges, especially since you originally said you were "implementing a new ISY-994i" (and not, interestingly, a new EISY). UD Mobile is a remote android/iOS app to the ISY-994 (no longer produced), the Polisy, and the EISY. I don't believe it provides the full spectrum of capabilities available from the Java interface to the ISY/Polisy/EISY.

Can be mixed, but light will behave only based upon to which switch it is connected. Responder levels for each responder in a scene can be unique to each controller device, and to the scene, itself (basically think of it as the EISY/PLM being the controller device).

I believe I have tried this in the past, with the same lack of success, but perhaps I will try again. The use of the "basic association" nodes was in response to the post from peterathans who apparently had success using these nodes.

It is possible that I am doing things wrong, or it is possible that these particular devices don't support it. I have added four zwave devices into a scene. For each device, I have only added the nodes "Basic Scene Ctl 2" and "Basic Assoc 2". There are two of each type of node and no other nodes in this scene, for a total of four nodes. Each device is added as "controller". I believe a couple of those are zooz devices, one being an outlet, and one being a dimmer switch. Two devices are likely other brands. I could find no combination of controller device that would allow selection of a "native", including trying to link the two zooz devices natively.

I have tried, but not as hard as you. One of the things I recall may be required is that the link type must be Z-wave and that not all z-wave devices have this capability (I was able to achieve it only with one device I own...a motion sensor). I have given up on trying to make this happen. Hopefully, someone else has had better luck and can help.

I have suddenly been curious about matter and reading up on a lot of terms…border routers, edge routers, matter controllers, matter bridges, thread, mesh. I percieve, for example, that (at this point) alexa border router/controller does not automatically link to a google router, but an alexa border router can share individual matter devices with a google matter router. Thread and wifi are, of course, different. From what I have read about the ISY, my,perception is that matter (wifi) devices will iintegrate natively with IoX. Matter (thread) devices will integrate only via a nest hub (gen2j or apple home. Interestin to me is that they did not mention any thread enable routers from amazon. I am also assuming that, at this point, IoX is not exposing nodes to other matter controllers via a matter interface. For now, I am assuming that this will still require a portal account. Maybe this will change in the future. Maybe my assumptions and perceptions are all wrong.

Based upon what I have seen, matter is not ready for prime time. I would not assume that we know much about how it will work, whether thermostats are supported, or whether it will stay linked for more than a few days. (Though, in fairness, I base my skepticism on thread, specifically, rather than matter as a whole.)

Shot in the dark....unlikely, I suspect...but is it possible that you have installed the Hue "Emulator" rather than the Hue

It has been my experience that, with Insteon switches, a "control" condition will trigger a program when the expected condition (on, off, etc...) is received from (and only from) manual control of the Insteon device. "Status" conditions will trigger a program any time an Insteon device changes state, regardless of what initiates the state change. If you are seeing behavior different than this, you may be having other difficulties, such as communication between devices.

Adding to this thought, I have several z-wave switches and none would trigger programs from a "control" (switched on) condition. A few would not even trigger status conditions. I start to wonder if, in the IoX world, the control condition is unique to Insteon devices. Perhaps Lutron switches also fail to trigger programs from a control condition? I second the motion to try "status" instead.

This is what I suspect is your problem.

Yes, it appeared to sign in correctly and show "linked".

This is what happened to me, as well. I can tell you that I do not have multiple gmail accounts and have only had a single gmail account ever.