oberkc

Yes. I shared it from the Alexa to the google home app. I do not recall any errors. I do not recall any mention of a thread network, but this may be my failure to recall. When I originally added it to Alexa, I did not, and still do not, have the nano leaf app. Perhaps that is a variable I should play around with.

I have the echo hub and have successfully added the nanoleaf bulb as well to alexa. I could also share it with a google nest and control the bulb from either device. I have also originally added the nanoleaf to the google hub and shared it with the alexa devices. In all the various combinations I have tried, the nanoleaf would loose connection eventually, sometime reconnecting, sometimes not.

For a standard (matter) that purports to be universal, why would there be? Why would there need to be? There was not setup or configuration information regarding "works with Alexa" or "works with google", either. Are they going to prove the comic to be prescient?

Yes. Agreed. I even tried a few variations. I reset the nano leaf bulb and tried adding directly to UD Mobile (android). No luck. I reset the bulb, moved it closer to the nest hub (gen 2) and added back to google home. I then shared the bulb from the google home app (android tablet) to UD Mobile (also android). No luck. I have tried variations of this using iOS devices with similar lack of success.

Well...just tried adding a couple of matter devices. One is a Cync bulb and wifi. The other is a nonoleaf bulb and thread. Both were prior added to google home and shared with apple (but not yet amazon). I now shared both via a qr code from google home. Both appeared to add (certainly got no errors). The thread device is taking a relative long time and is adding as I type this. Edit: and I come back after 5 hours of "adding" the thread device and find that it has not added and is stuck on the screen saying "adding matter device". The matter wifi device added fine. I may try some different approaches soon.

OK. I will assume that the upgrade took hold and will try some matter devices soon.

I just tried "upgrade packages" on mine (Polisy, wired). Formerly 5.9.1. No change after upgrade. Still shows 5.9.1 I am inclined not to ssh for a variety of reasons, not the least of which is that I am more comfortable (less perceived risk) in using the official method and waiting for an official announcement.

I think Guy Lavoie gets the prize! The only thing that would cause the keypad button to come on (besides directly pressing it) is when the hutch scene is turned on. No other scenes will cause it to come on and no other devices will cause it to come on.

I am certainly in that boat as well. I have most of what I want and don't need matter to add anything that is missing. I would just prefer local control for my voice assistants (at least when I am using the touch screens of the assistants) and access to a couple of items on google and Alexa that don't integrate with ISY. Regardless, my system is quite useful.

That is a little disappointing. I assume that matter devices added to ISY can be shared with other hubs through the portal, at least. Ultimately, I was (am) hoping that the ISY will become a matter "bridge", where it would expose all linked devices (matter or otherwise) to other hubs via the matter standard or be able to incorporate devices shared by other hubs via the matter standard. I have the same hope that the Echos and Nest hubs also become matter bridges. I assume that the _13 version will soon be published. I will wait. I don't do enough of the ssh stuff to be fluent. I have to look up how to do this each time.

Once added to the ISY, can one share a matter device to google or Alexa or apple home? I have not seen this instruction. Is this unique to the new (quietly released) software version?

I hope you are correct. It is statement like below that gives me concern:

From everything on this forum that I have read, it seems to me that the problems are more widespread than this response suggests. Do you suppose that they don't yet recognize the problems, or that there are steps that we are all missing?

I still think your program is incorrect. Are you simply trying to send yourself a reminder when it is Feb 7th (holiday or otherwise)? Are you trying to send yourself a reminder on a particular Sunday? When do you expect your program to trigger as true? On Feb 7th? on a Sunday? On a Sunday which happens to be Feb 7th? Other? On what day this year did you expect your program to be true but it was not?

As I understand the Holiday nodes, this program would only be true if February 7th falls on a Sunday. That did not happen this current year. What are you trying to accomplish with this program?

I don't see a way to add a matter device to UDMobile via code...only by QR. Sharing from google home can provide a QR code, but Alexa does not. I don't see how apple does it, but I do not have an apple matter router. I have hear someone found a way to convert a numeric code into a QR code. Regardless of all this, I don't believe the UDMobile app is working yet WRT adding matter devices.

Perhaps it is no big deal. Since hearing about it and the possibility of ISY support, I was excited about the possibility that some of these alexa/homekit/google devices would work at a local level (no cloud reliance), not require the use of inceasingly limited wifi bandwidth, and the possibility that these various matter hubs (including the ISY) would expose their respective devices to the various other hubs and border routers….one happy family…all at the local network level. I do have one of those Brilliant switches. At one point, they were promising matter support but I suspect they are out of business at this point. I was hopeful that the promises of matter would ultimately bring exposure of ISY devices to he brillianr switch. Probably not going to happen now. yes, much of this capability is available with node servers and portal, but this remains too dependent on the cloud for my preferences.

I have the same two devices, plus two thread border routers (echo hub and google nest hub 2nd gen). No luck so far. Same, or similar, errors, depending on how I try to add it. They both add fine to google and Alexa, and both can be shared between the two and with apple HomeKit.

I pre-ordered my Polisy as soon as they were announced. I would imagine it was as early of a release as any. No BIOS updates for me, as far as I know (though there was a session I had with UD where they did a lot of fixing of things that I was unable to follow...perhaps they loaded this BIOS?). No problem since, including uneventful update. I have updated all the UD Mobile apps I have on android and iOS devices. I have synced them all. Everything that I see and can recognize suggests that matter is incorporated and active. I have yet to have, or have read about, a successful addition of a matter device into iOX.

I am not even sure that I want Alexa+. I understand it may use cameras (which I have blocked) to supplement the information available and to provide a "better" response. No thanks.

Yes, that took me a while to understand that every room, scene, and device created in the hue app shows up as a node in the ISY. I will delete those for which I have no need to help avoiding some confusion. I cannot say, however, that I have ever experienced a hue device that shows up in the hue app not register in the plug-in. I am glad you got it working.

Correct. Correct, alternating with bright commands on each successive press-and-hold.. Perhaps that is the difference. I experimented with direct connection once and went back to the hue hub/PG3. The direct connection did not, as I recall, have the full set of features.

I know of nothing unique about the configuration of the keypad button. It is, in this case, button F of an eight button dimming device. Perhaps more telling is the configuration of the scene. I have attached a shot of the scene definition, from the keypad controller viewpoint. I use an "set xy color" rather than "default" or other action in response to the keypad scene initiation. I wonder if this makes a difference.

I have an Insteon device (keypad, in this case) as scene controller, and hub bulb as scene responder. If I press-and-hold the keypad button, the hue bulb dims/brightens. No programs. Nothing but a scene. Works great for me. Is this not "real time control, manually"?

I am not sure that I understand this entire thread. I have Insteon devices as scene controllers and hue bulbs (via PG3 node server) as responders. They brighten and dim just fine when so commanded by the switch. Am I missing something?