Guy Lavoie

Not what he did but if he could ssh to it with the IP address, then https://<ip address>:8443/desc would certainly work. That's the way mine is set up.

Did you update the firmware in the bulbs? Should be 4.1.3

Well, I did find one thing about the border router in the Echo being created "automatically". From: https://www.amazon.ca/gp/help/customer/display.html?nodeId=TSWevY1sX8ADH2LC20 "Compatible Echo devices can act as Thread border routers. These Echo devices automatically create a Thread network and store Thread network credentials on your Amazon account. When you connect a Thread Matter device with your Echo, your Echo retrieves the Thread network credentials for easy setup." That seems to confirm my initial thought that routing across it should be transparent. I did run into another thing that I noticed with the Nanoleaf app. When it adds a bulb, it looks for a matter network. It finds one and says it will add the bulb to the network, but then says that fails, so it gets added as a bluetooth device. Yet adding the bulb directly in the Alex app (add, other, Matter) works fine. From various searches I've done, it looks like the Nanoleaf bulbs are very inconsistent with linking to various Matter controllers. They probably debugged the most common ones like Alexa and the rest remain flaky. I'd love to try and just share it from the Alexa app, but until either the Alexa app can provide a QR code for sharing, or the UDI app accepts a 11 digit pin code, that won't be possible.

This is an issue that's known to sometimes happen with the update, and is almost always recoverable. UDI strongly prefers that you open a ticket.

Well if Google Home is providing the credential information, but the eisy can't then get to the bulb itself (through the border router), then that could explain the problem. There seems to be no real set up or configuration information of the border router itself. I've been wondering about that. Nothing in the Echo device either. I know it's IPv6 to IPv6 so technically it's just a physical layer thing, wifi to Zigbee. It almost sounds too simple.

So you were you able to add the shared Cync bulb to your eisy ok. (I'm also experimenting with a Cync and Nanoloeaf bulb). Looks like it worked because Google Home is giving you a QR code for sharing, while Alexa and Hue only give an 11 digit pin code. But it's still strange that the shared Thread bulb isn't working, esp coming from the same Google home app that worked for sharing the wifi bulb. So each bulb gives you it's own sharing code? This is different from the Hue hub which seems to be giving you a single sharing pin code for everything on that hub. Then again, Hue is exposing the devices as Matter bulbs, even though the bulbs themselves aren't. If/when UD Mobile is updated to accept an 11 digit pin code for adding Matter devices, it will be a lot easier to try it with Alexa and Hue.

The REST functionality is alive and well. If you can get your text message to send a http GET request to your Polisy, that should work. the hard part will be getting the text message response to your local network and interpreted.

You would do that here: https://www.universal-devices.com/my-tickets/

Have you tried testing something like a lamplinc in that other building, to see if insteon signals can get there? If not, then IP based devices might be an option, since your network goes to it. What type of device are you looking to control?

Can you ssh into it? ssh admin@eisy.local If so then you should be able to recover without needing to restore from backups. Look at this thread, scroll down to tokenworkers post. Otherwise you can open a ticket. https://forum.universal-devices.com/topic/44914-brand-new-eisy-update-failure/

Good, great that you cleared that up for any other iOS users.

Well that's actually good: different tests with different devices. Up until my last test, I was thinking that a border router was strictly a networking device. Now it seems that it's also usually the initial commissioning device that the bulb or whatever will belong to, and be shared by. Mind you, this is a sample size of two users... So contrary to my Hue hub and Amazon Echo, your controller can generate a QR code for sharing. Now when you say that adding the shared Matter device with UD Mobile "never works", are you using the IoS version? That is known to not be working yet. We're both hampered by one thing missing in the chain. That's how we learn! Let's keep trying.

Welll you wouldn't see the incremental upgrade (to 5.9.1_13) that way. You really need to view the information in the sysconfig file to know. https://eisy.local:8443/WEB/sysconfig.txt that's how I saw my Polisy go from _7 to _13 when I did the pkg install. I estimate the the pkg install command is "safe" because it's not like messing around with individual files. It really is how packages get install and/or upgraded, albeit usually as part of scripts.

From my (very limited) experience so far, an already commissioned device isn't "found" by UD Mobile when you try to add it. It just keeps finding other bluetooth devices that aren't Matter devices, then tells you none were found. Factory resetting the bulb will allow it to be found again. You'll quickly learn the joys of factory resets (often by powering the bulb on and off 5 times or so) while experimenting with this. I finally got my Echo device set up this morning. The Alexa app quickly found my Nanoleaf bulb (Thread) and added it. Then I went into the device configuration and tried to share it, but just like the Hue app, it only gives me a numeric pairing code, while UD Mobile only accepts a QR code. So close... I'm still trying to find a way to convert a pairing code to a QR code, though that's not straightforward because a Matter QR code contains more then just a pairing code. There is vendor, version, etc information in it too.

Did you already have an earlier 5.9.1 when you did that?

Yes. It works with the android version of UD Mobile. You also need the latest iteration of 5.9.1 in your eisy or Polisy, which as of Monday was 5.9.1_13. From what I can tell, forcing an upgrade when you already have an earlier 5.9.1 requires going in by ssh and issuing a pkg install command. The first Matter device I was able to add was a wifi bulb. I just got (like an hour ago) a 4th gen. Amazon Echo, which has Zigbee and the needed border router functionality. I should have a chance to install it tomorrow and try out installing my Nanoleaf bulb, which is Matter over Thread. I'll report back on that when I get a chance.

I don't know anything about it myself, but there are many videos on youtube that cover it.

I added a dual band lamplinc in the garage to help with signal reliability. Has been working fine.

If you can ssh into it, you might try this (though it's not UDI's preferred official approach...your judgement call). It worked for me. Scroll down to tokenworker's post, describing the pkg install commands in bold. Please read the whole thread first.

Great, glad it helped! You really gotta view the KPL buttons as miniature Insteon switches, and their backlights as loads switched by them, or by scenes they are responders to, just like regular Insteon switches. Being a bit of a status tracking nut, I have many scenes that I call "reverse" scenes that exist just for the purpose of updating a KPL backlight for a button. Any other thing that might activate a switch(es) controlled by a KPL button gets added as a controller to the reverse scene, to keep the button's backlight up to date.

Yesterday I configured a Matter bulb with an android phone.

If the light is triggered from another scene it won't work. You would need to add your KPL H button as a responder to that other scene.

I'm sure most of that will become clear over time. This is still beta. Just getting the communications and device linking working reliably is certainly the most important first step. UDI is arriving at that. Most of us here already have working systems so going to an all-matter setup would be the exception. I want to enjoy learning and understanding the topology early on. I'm in no rush to set up anything in particular at this point. I'm quite confident that the eisy will indeed be able to make all device types work together. We already see it with scenes. Insteon is the "mother tongue" it's designed around, but you can put zwave, zigbee, Matter devices in scenes and they work. I did test the Matter bulb as a scene responder yesterday, worked fine. For other things, programs can be used. It will be interesting to see if as you say, other devices can be mapped to a Matter equivalent directly. If not, as scenes or through programs.

The ISY doesn't seem to have a Matter sharing function, yet. That's why you need to choose your root device wisely. I still need to test some other things, one of which is to encode the Hue hub's Matter sharing pin code into a QR code, and try adding it to the eisy using UD Mobile. I'm looking into a QR code encoding utility for that. I don't have a border router yet (looking into getting a used 4th gen. Alexa Echo for this), so the Thread bulb will have to wait. Not sure I understand your question. The Iox launcher hasn't changed. Still the same as it has been with 5.8.4.

A few more notes: - Following the eisy upgrade from 5.9.1_12 to 5.9.1_13, I was able to add the bulb to that controller too. So make sure you have 5.9.1_13 before trying anything else. So Matter over wifi works without needing the ZMatter dongle, as it should (though the default device name will start with ZM...). Deleting the bulb from the Polisy wasn't enough to make it configurable, I really needed to factory reset the bulb itself. So it looks like Matter devices can only belong to one main controller, and then shared by that device. So choose your main controller carefully if you have more than one that can add Matter devices. - I tried adding the Thread bulb to the Polisy (because it has the dongle) but that didn't work. In fairness, the release announcement does say that a border router is needed, at least at this time. - When adding a Matter device, it does take a bit of time to first find the device after scanning the QR code, and then you will see that your controller does an "interview" process in a pop up window of the admin console. - It would be handy to allow the UD Mobile app to also accept a pairing code instead of just the QR code. Some devices like the Hue hub only offer a pairing code for doing the share process.