Javi

The short answer is if you do not have good cell service geofencing will not work, and/or will require a wider fence. Wifi Range in not a good indicator for the various reasons listed above (faux mac addresses (iOS), wifi sleeping, or a dead spot in the corer of the room). Ble has it's own issues even worse than WiFi for this sort of situation. If your router supports, you can trigger something when your phone connects, but you will have the same issues. There are vehicle gps systems that can send geofence triggers, this is likely the best in your case, although for most of us a city with high concentrations of WiFi access points and cell towers geofencing works good enough without the extra fee of the vehicle gps system. While UDM, and any other app, can read an SSID it can only do so in a foreground request. Apple does not allow apps to read SSIDs in the background (without it being a special category of HotSpot, we have asked apple and have been denied, the app must be for a HotSpot). Also many background request are queued so the request and the response may be minutes or hours apart. Geofencing uses a number of indicators, like GPS, WiFi access points, and cell towers. GPS is not always on or your battery would die in a few hours. Wifi is not always on for the same reason, although it would last a few more hours. So your phone periodically wakes, connects to Wifi, then check may things or allows apps to do a queued background update. This wake may check fences, I say may as there are other indicators as is more complicated than my simple explanation, you don't want your phone checking GPS ever X-num of minutes or the battery would die.

It looks like it last triggered at 3:13 PM as an exit, so it is working. The app's geofence logs will show all entries and exists along with any communication errors. https://wiki.universal-devices.com/UD_Mobile#Geofencing I say usually as the fence notification is handled by the OS, not the app. How the OS does things differs depending on may variables such as platform (iOS/Android), OS version, battery level, privacy settings, location settings, and MFG (in the case of Android). The Android App can do things to change this behavior (UD Mobile Location Services Section in Wiki), but on iOS it is mostly controlled by Apple. The most important thing is setting, both the OS Global and App Location Settings must all be enabled or fences may not work.

I recommend using UD Mobile Geofencing. Geofences use WiFi (including access points which do not belong to you) along with GPS. If using Wifi only it may change the variable when the when the screen is off for long periods, which will cause the variable to change even when in range. Geofence lookup is usually triggered when the device connects to a WiFi access point.

I think we have your ticket, if not please open one.

Fixed in 1.5.10

Replicated, working on a fix. The issue is the app fails to synchronize after name change. Synchronizing should update.

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.