Javi

The icons are gray in the screenshots so the connection is lost, attempting anything in the AC when the icons are gray may have unexpected behavior.

As with every protocol, there are advantages and disadvantages, and in this case there are a few Wifi, ipv6, and Matter. There are network hardwired matter devices which likely will not have the same issue, same as the tread matter devices. Being as you have multiple devices with the same symptoms, my guess is the root cause is the WiFi device and WiFi router do not play well together sometimes. When issues like this were encountered with some testers it was usually solved by disabling all bands except the 2.4Ghz (not ideal), or replacing the router. Both seemed to solve the issues.

I'm not sure, I can not replicate. If not on 6.0.5, it is possible there was a bug which was fixed in 6.0.5. Is there an error message?

6.0.4 has an issue on large installations where some initial status values are dropped. Not every time, not always the same status values. What were the issues in 6.0.5?

Great

I'm not sure, if synch does not show errors then something is missing in the configuration. UDM will prompt for backup if it will remove anything not updated after synchronization. Does it suggest creating a backup? First try legacy synchronization, Settings Tab > User Preferences > Use Legacy Synchronization, then synchronize. Edit: You must be on 6.0.5 there are known issues in 6.0.4.

Assuming the device was added to the other hubs using a Pairing Code, and not connected via eisy, then it points to device itself being the root cause of the issue. We have also encountered this, but not something we can troubleshoot, sometimes power cycling the Matter Device corrected, but not always. The Matter Device likely connects to the MFG's cloud but does NOT use the Matter protocol, as they would need a connection to a Matter Controller on your network. So very possible the device is online but it's matter implementation failed. So this would explain their app and their Alexa integration via cloud working, while all matter connections fail.

Are you on the latest firmware? If you are please open a ticket.

Synchronize, required after a recent app update.

If eisy or Matter Device reboot does not correct the issue, then re-adding may by the only option. If this device is NOT connected to any other service (Google/Apple Home or MFG's app) and the device is simple to setup (i.e. not a complicated setup like a thermostat) then factory reset the device prior to adding again. If the device IS connected to an MFG's app or difficult to setup you must delete the device from eisy, then delete eisy's service (admin) from the Matter Device. I added instructions to wiki: https://wiki.universal-devices.com/UD_Mobile#Matter_Device_Reset Most of eisy's Matter issues in the past were related to adding devices or adding controls/properties. Other status/connection issues are usually related to Networking, networked matter devices have the same issues as other WiFi devices (dropped network/ authentication/ etc). When I could isolate the issues they usually correlated with dropped WiFi networks or network/wifi restoration timing after power restoration As you have noticed, this is not limited to eisy. I have not encounter the same with matter over thread, assuming the boarder router is working.

Did eisy firmware 6.0.5 correct the issue?

Issue should be resolved in yesterday's firmware release.

Likely in eisyUI + remote. Latest eisy UI release has some mobile ui improvements.

There are logs in Settings > Geofence > Document Icon at the top right. Usually due to network issues, may require a slight increase in the fence radius.

Issue located. Fixed in UD Mobile Android 1.5.8. Not yet released.

The message is sent by eisy, through the Plugin Notification group. The group can be disabled in UDM > Notification Tab > Mobile Devices/Groups > Groups. The available was not updated on server side, so it is incorrect. If on 6.0.4 check eisyUI for upgrade specifics, eisy.local/system/upgrade

If issue persists please open a ticket with new logs. Looks like 2 errors. In one instance it could not reach my.isy.io possible DNS issue. The other is the connection was forcefully dropped while sending the command, possibly due to network switching or timeout waiting for DNS resolution.

It should respond.

It does, but it is actually a scene used so eisy can observe status of all devices. Icon is a monitor, see @Geddy 's image.

Please update to 6.0.4. Sync should not be slower, but there is less info is shown in progress, so current process remains longer. Manual delete of eisy Node Properties databases may be required. However a firmware upgrade usually fixes this also. If not fixed by 6.0.4 please open a ticket.

It may be a different name like "ISY" or "IoX" depending on when the original file was created or if renamed. Icon should look like a monitor.

@Techman , I misunderstood the request. You are trying to send all off to the ISY scene. We do not show this scene in UDM as it would likely cause confusion. The work around used by @IndyMike sends the same command to the ISY Scene.

iOS version is in review now, so likely live in the next 1-12hours. If this does not correct the issue, please open a ticket, include UUID

Not normal, but cannot test on 6.0.3 as the current patch is 6.0.4 which has bug fixes. Also UDM 1.4.15 is awaiting apple's review so should be released soon, so also worth a try after upgrading to 6.0.4. If issue persists after upgrade try to disable each of the controllers to check if it is isolated to one (Home Tab Menu > Controller's Settings > System Settings), cancel requests to synchronize. The reason is one controller may be publishing too many status updates causing UDM to appear slow for both controllers.

I can not replicate this behavior, both Conditions and Actions show the path in Admin Console on my eisy. Are you sure the device is in a user-created folder, not the main folder? The default name for the main folder is iOX, but may have been renamed by user, the icon is a monitor. If in this "folder" it is at root.