Guy Lavoie

Got a little further...essentially replicated your test. I was reading up a bit more on Matter and discovered that even a 1st generation Google home mini supports Matter. I have had one sitting here for a couple of years, that I bought used for $15 when I was first checking out Alexa and such. I hadn't talked to it in all that time (poor thing!). So I fired up the Google home app and added the bulb, manually entering the pairing code (both that and QR options were available). Success...I can turn the bulb on or off in Google home, and vocally with the home mini speaker. This at least told me that IPv6 was working. Then I looked up how to share the Matter device with external apps, and did the "email the screen shot" thing to have a QR code to scan off my computer screen with the UD Mobile app. As expected, it gives me the 500 error. It really looks like UD is missing a piece somewhere. Just nice to know that we're all on the same page. I'm in no hurry, and the learning experience is certainly beneficial.

Off the top, that looks correct, though I've never personally configured a scene command via the portal. I would imagine that a Alexa category called "scene" would operate like Insteon scenes, responding to on and off commands. Can anyone else concur? Does the scene itself turn on and off ok from the admin console?

Which phone app? I look at the foldout sheet that came with the Cync bulb and it has two sets of instructions, one for setting it up with the Cync phone app (which I haven't tried yet), another set for "Connect directly into your Matter-compatible smart home system". The third page then says that you may set up the bulb for use with the Cync app or Matter, but not both. For the Matter setup, step 1 is to screw in the bulb so it lights up, then step 2 is "open your preferred Matter compatible app on your smartphone", and follow the "Add device" instructions in the app. Once again...how does the bulb get access credentials to my network? Are all Matter compatible apps using BLE to access the bulb? Is UD Mobile (I really don't think so)? From the reading I've been doing on Matter, it is principally a sharing mechanism more than a base protocol. Thus the reason for the use of pairing codes. I get a sense that Matter devices aren't all created equal. To borrow a few terms from Insteon, some are responders and others are controllers. For example, the Hue app allows you to generate a pairing code so that another system like Google Nest can control the bulbs, so the Hue hub would be a responder. But the Hue app can't (at least not yet) control other non-Hue devices. Google Nest hub seems to have both responder and controller capabilities, and can thus act as a router between two systems. Now we come to UDI...the release announcement says: - Matter Initial support for light bulbs and plugin modules: -- WiFi direct. -- WiFi through a Border Router such as Google Nest Hub or Apple HomePod. -- Thread through a Border Router. The first line "-- WiFi direct" seems to imply that it could control a wifi Matter device directly, like my Cync bulb. I think that's what most of us have been thinking, and trying. But this brings me back to my initial interrogation: how can the bulb first get recognized on my network? Seems some kind of setup is needed, similar to how we usually configure standalone network devices (eg: connecting to it as a wifi hotspot and telling it our SSID and password). That's the step that seems to be missing.

Could you post a screen shot of the definition of the master suite device in the portal? Like this:

Take a screen shot of your admin console while displaying the Keypadlinc node for the E button, like below (that example is for my "A" button) and post the image. We want to see the Membership list as shown on the right hand side.

So if I understand you correctly you were able to: 1- Add a Matter device to a nest hub 2- Share the device known by the nest hub to the Alexa echo, using a QR code generated by the nest hub (through a nest app?) 3- Try the same QR code (generated in step 2 above) that was accepted by Alexa echo in UD Mobile, but that failed. 4- You're saying that if you wanted to try scanning a QR code with UD that was generated by the nest app running on android, you'd need two phones, because one would need to scan the QR code off the screen of the other... though you could probably take an android screen shot (usually power + vol down), email it as an image from the gallery to yourself, open the email on a PC, and then scan the code off the PC screen. I did in fact use that trick when I tried to scan the Matter code generated by the Hue app (as a number, converted to a QR code by a web site). The UD app showed the sharing code number correctly, but gave it a 500 error. So in all that, still not a single Matter device successfully added to your eisy... I get a sense that it's just not possible yet. There seems to be a piece missing. Either that or the requirements as listed in the release announcement aren't clearly explained.

Well that would be whatever the actual command you are using would be. I was assuming that you had this set up already and that you had noticed that the door would activate no matter if you asked it to open or close. If you haven't really set anything up yet, I would suggest that you set up the garage door device in the portal to set a variable, to make it single triggering. It would be something like this: Make the Alexa Open command set (let's call it the Door_command_variable) to 1, and the Alexa Close command set it to 2. Now the program logic would go like this: If Door_command_variable = 1 And Tilt sensor variable = "closed" Then Open door Then Door_command_variable = 0 If Door_command_variable = 2 And Tilt sensor variable = "open" Then Close door Then Door_command_variable = 0 Setting the variable back to 0 makes sure that nothing will happen until a new, valid command is issued.

I also tried adding a Matter device with a GE Cync bulb. QR code gives the same "500" error. But as an IP device, how does something like a new bulb fresh out of the box get access to my network? Seems it needs network access first. Is the Matter inclusion app doing some kind of UPNP scan? That aspect of it isn't clear. Another thing is about those QR codes themselves. It's just a sticker on the bulb that easily falls off. If you lose it, I can't see how it could be recovered, unless there is some kind of network scanning app that could look for valid devices. At minimum, we'll need to write down the digits (xxxx-yyy-zzzz) that seem to form every Matter pairing code, so we can at least regenerate the QR code if needed again.

For sure! Local control is our fundamental religion. Anything else like web access is just nice to have on top.

I've created two icons (open and closed garage door) and I've accessed them as URLs on a local PC, which works fine...unless I'm away from home. A remotely accessible URL like yours is certainly better. What I'd really like is to be able to import the icons into UD Mobile, as local files on my phone. Alternately, is there such a thing as a web server app that we can install on a phone (android)? I see several listed, but I'd like to know about any recommended, known safe ones.

This is where AND statements come in. Here is generic logic that you could use to create two programs: If Alexa open door command And Tilt sensor variable = "closed" Then Open door If Alexa close door command And Tilt sensor variable = "open" Then Close door You wouldn't have anything for Else statements.

I have the updated android app. As a test, I tried adding my Hue bridge as a Matter device. I went into the "Smart Home" section of the Hue app to generate the Matter pairing code, which it gives as a numeric string. Then I went to a web site that allows you to generate QR codes from text, then tried scanning the resulting QR code with the UD Mobile app. It gives me an invalid code error for adding Matter devices. Was worth a try...

Running some programs at startup is a way to immediately set certain things to desired initial defaults, where there are not necessarily triggering events that occur. For example you might want to test if your alarm system is armed or disarmed, assume that your sprinklers are off, etc. Regular programs usually run only when certain triggering events happen.

The "need" for the Zmatter dongle hasn't really been made clear yet. In principle, it should be needed (or an option) for Thread devices, though the 5.9.1 release announcement doesn't mention it, and instead indicates that Thread could be done through "border routers". As announced: - Matter Initial support for light bulbs and plugin modules: -- WiFi direct. -- WiFi through a Border Router such as Google Nest Hub or Apple HomePod. -- Thread through a Border Router I'm guessing that ultimately, the dongle would be an alternative to the border router.

Upgrade to 5.8.4 or to 5.9.1? The current "upgrade" is 5.9.1, and a few Polisys have gotten bricked in the process. Looks like that might be your case. You'll need to open a support ticket on that.

Nice to see that it was recoverable, and good to know for others who experience the same problem. Good support from UDI.

Has anyone, anywhere successfully linked a Matter device yet? If so, what what is the device? How did you proceed?

Ticket time.

There is nothing wrong with using multiple programs, and it's not a question of efficiency. Complex, nested logic requires multiple programs like that.

Plugins are used with the controller itself, to extend functionality and add new features. They're not specifically related to UD Mobile. For example the Hue plugin will allow you to control Philips Hue bulbs, they will appear as devices you can then control. Ask a more specific question.

Sounds like it might be a firmware issue in the opener's controller, especially if the trouble reported by others are for people installing new openers.

Interesting, because I picked up one of these just last week (as an open box item on marketplace, for a ridiculous price). I already have a well functioning garage door setup with an Insteon IOLinc. I just thought I'd give it a try and see how it goes, and learn along the way, for possible use if worthwhile. I installed on on my eisy, which has the Zooz 700 series dongle. It took a bit of fiddling but it linked and installed ok, and does appear as a barrier device as you say it should. Works correctly too, as I simulate the door movement with the tilt sensor in my hand. My device list shows 5 nodes; the ones you listed plus "Unattended Op alarm". Are you using a Zooz dongle or the Zmatter one?

I just tried that (thanks for drawing my attention to it). Unfortunately it doesn't work. If I try to set the color or saturation levels, I get a "could not get brightness node" error. But the brightness level works fine, like a white only bulb. As part of the testing process I switched the bulb over to the Hue hub network and did a software update on the bulb, hoping that it would fix this, but I get the same result after deleting it from the hub and reacquiring it with the Polisy. This might be one of the older versions of the bulb. It had firmware 67.88 and it upgraded to 67.116.

I just tested linking a color bulb. It works, but I can't see any way of changing the colors. It looks like it sees just a Zigbee on/off switch, though dimming works fine on both bulbs I tested. But why are you specifically looking to remove the Hue hub, given that you already have it?

It works! I screwed in a brand new Hue White bulb, fired up the Polisy, and chose "Add a Zigbee Device" under Zigbee. It saw the bulb right away and added it. The bulb also blinked on a off at least a dozen times before just staying lit. Looks like this in IoX