
oberkc
Members-
Posts
5835 -
Joined
-
Last visited
Everything posted by oberkc
-
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?
-
It might, but I don't suspect this to be the case. I understand that the major point of matter is being a universal standard, shareable regardless of manufacturers. To that point, I have successfully added matter devices (both thread and wifi) to Alexa, then share them with google. I have also added matter devices to google and shared them with Alexa. In no case have I been able to add any directly to UDMobile, or share via google/Alexa to UDMobile. As far as the Cync bulb app, I wonder if it even uses the matter standard. My guess it NO and I suspect that may be the reason that the bulb cannot be paired with both app and matter hub.
-
I have android version of UD Mobile. There was a recent update that added the capability to add matter devices, but only via QR code (not able to type in a numeric code). I do not use Home Assistant, but Google Home has the ability to share a paired device via generating a QR code (Alexa does not, as far as I can tell). I have not seen the ability to add matter devices on iOS version of UD Mobile. Unfortunately, trying to add a matter device using UD Mobile has been a failure for me so far.
-
I am still trying to understand the whole matter thing. My perception so far is that once a matter code is used to pair with one hub, the same code cannot be used to pair with another. Instead, the original hub must share the device with the second hub, generating a new code. I don't know if that is what you tried but I suspect it would not matter...you would probably get the same results.
-
I look forward to hearing the results. I do not recall a post from anyone claiming success adding any matter device.
-
Your experience sounds similar to mine in some ways. Some z-wave devices I have tried do not seem to update status in the ISY when controlled locally. I have decided that I am not going to use Z-wave devices as scene controllers. They work quite well for me as responders, however. I have only used z-wave as part of the ISY/Polisy so I cannot compare that to other systems or know whether this is normal for z-wave or unique to Universal Devices.
-
Yes, older generation nests support matter (wifi). Only gen 2 nest hub has the thread capability. I am unsure which, if any, of the nest speakers include thread.
-
I can tell you that my Cynd bulb (wifi) connected to my matter controller (nest hub gen 2, in this case) without having to input wifi credentials. Yes, this suggests that my credentials are now at greater risk of becoming part of the next data breach. I am not sure what to think of this.
-
Sharing with Alexa could probably be done with a QR code, but the nest hub has that option built in directly, and it worked for me. Furthermore, while I cannot confirm it, I suspect this may be the method that puts both (echo and nest) matter (thread) routers into the same network. No, I generated a new QR code specifically with the intention of trying to link with UD mobile. This would not be the same QR code that one would use for Alexa or Apple or whatever. Yes, but your trick might very well work. I found it interesting that the iPad app for nest hub did not include the sharing-via-QR-code option. Only the android version did this. I also found it a little disappointing that the UDMobile app did not include the option to add matter devices via manually entered (or copy/paste) numeric code. The two devices I have include a sticker, as well as being printed directly on the device.
-
I agree...it is not intuitive to me. I tried adding it directly with UDMobile scan. Error. I then added it to nest hub (worked) and shared it with Alexa echo hub (worked). Unlike the Echo, google home can share connected matter devices via a generated QR code (Alexa can share only with a numeric code.). When I use UDMobile to scan the QR code generated by Nest Hub: Error. I also notice that the nest hub app only generates a code with the android version. And iOS version of UDMobile is not quite ready, I understand. This means that to do all that I tried one needs to have two android devices in order to share a matter device with ISY. I keep hoping I am missing something. I am glad I am not anxious to get a matter device to work. As far as I can tell, matter is not ready for prime time.
-
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.