mmb

Your Iolinc is behaving exactly like mine, same settings.

In a previous by Michel, he indicated they are reworking the Matter drivers because they were written for Linux, not BSD. Has this been resolved?

Discussed back in August 2023.

Anything in the Error Log?

I read the ZMatter libraries are written in Linux whereas UDI controllers are Unix. Kind of a wrinkle, but they are working through it...

My Dad is content with his ISY on 4.7.5. His setup is pretty small and his automation needs are pretty basic - about 10 different programs to make life easier. I'll leave it alone. My setup is much more complex - 30 or so programs, PG3 MQTT, REST python servers , Z-Wave, Zigbee. Polisy on 5.7 is great.

Thanks @RPerrault, in March 2012, Smarthome began shipping new devices using the i2cs protocol. In any event, seems like a lot of work to reset device protocols for little gain if everything is communicating properly.

@Brian H I found your comment regarding I1 protocol interesting. I checked communications for one of my switches which is a dual band 2477S V .42 and it's communicating using I1 protocol. Do you know what switch version started using the newer protocol? I'm not experiencing any communication problems.

Maybe shrink the Home screen icons a bit and a feature to select certain Favorites on the Home screen?

Polisy updated fine no issues.

Javi, UDM is looking really good and really like the Favorites icons and all. Question: The Home screen is rather empty and could easily handle all the main icons rather than a More ... icon. Are there plans for this space? Great work!

I presume Polisy would be included in this integration?

I use this url to get versions on Polisy. https://polisy.local:8443/WEB/sysconfig.txt But yes, having About report version would be nice.

Checked my Polisy, my display is off by 1 hour as well.

Thanks just tried your suggestion but nothing appearing under battery level. I'll give it a bit of time because I remember when using the zooz dongle the level appeared the next day. I'll update tomorrow or earlier...

Interestingly I lost my battery level monitor on my Aeotec Multilevel Sensor when I upgraded from the Zooz 700 dongle to the ZMatter dongle. I tried resetting the sensor several times to get the battery level back without success. Temperature, Humidity and Dew Point reporting still work reliably fortunately. Fyi I never lost the node numbers on a battery reset, but have on a device reset which makes sense.

Anyway, thanks the detailed explanation, I learned something 👍

Thanks, I actually didn't try other devices but will if it ever happens again. To resolve the last instance of can not contact UD, I went into the GH app then into Settings/Services/Works with Google then scrolled to the UD module and pressed it. It took me to the portal screen for a login. After logging in the spokens started working again. I do remember having to re-link the UD module on previous occasions. Then logging back in to get spokens working again. I'll pay more attention to the specifics if it happens again.

Thank you, the disconnect results in a can not contact Universal Devices (or similar) on a spoken command. Does losing track of the "agentUserId" necessitate a re-authentication via portal or a re-link of the UD module then an authentication? As noted it doesn't happen often. I assumed it was related to a backend change or an app update.

Maybe @bmercier can help me understand why Google seems to disconnect from time to time which requires either removing the UD link and re-adding or re-authenticating to link up the service? It happens only a couple of times a year with Google but Amazon has been rock solid since I linked it. Just curious, thanks. (sorry if I should have made this a new thread)

I actually had this problem on Saturday out of nowhere -"can't reach UDI" The usual fix of going into Google Home app and linking UD and authenticating fixed it for me.

You can mark the solution and leave it. It will help others and live on…

@DualBandAid I assumed too much. My USB zmatter dongle was the root cause of my initialization forever. Changing the port fixed it.

I had this happen several times and submitted a ticket for the problem. I resolved it before a response. Check to see if the z-wave and zigbee tabs work properly in the AC. Are you using a USB hub? I my case the USB hub was the problem, simply changing the USB port on the hub fixed it. Why it happens, not sure.

I highly doubt the timelines are current if there's anything...