I replaced 3 of my Insteon thermostats that have controlled my zone heating for many years. They were beginning to fail, so I decided to replace them with Meross MTS300 matter enabled thermostats which are a very cost effective solution. I have been very happy with the performance of them thus far.

I added them to the Meross app and configured them all. I then tried to add them to the UD Mobile app without success. After reading some of the forums, I decided to follow the suggestions and add them to Apple Home app first and then to the UD mobile app. I was able to add all three of them to the UD Mobile app using the multi-admin capabilities by generating a code in Apple Home and was able to successfully add them and manipulate them in UD Mobile. I then checked to see if I could see them in the eISY UI. I could see each thermostat. That was a few days ago. I noticed today that one of the thermostats on the UD Mobile interface shows blanks for all of the values. eISY also shows one of the devices with an "exclamation point" and no values. I can still see them in Apple Home and in the Meross app and responding properly.

My question is what is the proper steps to solve this? Can I just delete the thermostat from eISY and UD Mobile and re-add it? Do I have to clear a cache or other marker in the software that will prevent it from adding again? I know the universal devices matter is still beta, so I want make sure I do things right and don't lock my devices out of this environment.

Any suggestions?

Up until now, the few of us that have been dabbling in Matter have been doing so on an experimental basis, knowing fully well that having it operating reliably on the eisy might take a while yet. If your thermostats are otherwise working correctly in Apple Home, I don't see any harm in deleting them and adding them back in the eisy. There was also a IoX update just a couple of days ago (to 6.0.5) that includes unspecified improvements to Matter, so it would be a good idea to do that update now if you haven't already.

Unfortunately, based on my experience so far, adding matter devices to Alexa/Google/Apple/EISY only to find them losing connection later, then gaining it back, then losing it again, is not uncommon. This happens to me regularly and not just with the EISY. This morning, for example, one of the devices I added yesterday lost connection with Alexa.

Sometimes I find that trying to turn on/off the device from one of the hubs will re-establish communication. Sometimes, power cycling the non-responding device can work. I have had some matter devices simply drop wifi connection. Sometimes, nothing works besides deleting the device everywhere, factory resetting the device, then re-adding.

Still, it seems as if matter is making progress, if a bit slowly.

52 minutes ago, mdarcy said:

I replaced 3 of my Insteon thermostats that have controlled my zone heating for many years. They were beginning to fail, so I decided to replace them with Meross MTS300 matter enabled thermostats which are a very cost effective solution. I have been very happy with the performance of them thus far.

I added them to the Meross app and configured them all. I then tried to add them to the UD Mobile app without success. After reading some of the forums, I decided to follow the suggestions and add them to Apple Home app first and then to the UD mobile app. I was able to add all three of them to the UD Mobile app using the multi-admin capabilities by generating a code in Apple Home and was able to successfully add them and manipulate them in UD Mobile. I then checked to see if I could see them in the eISY UI. I could see each thermostat. That was a few days ago. I noticed today that one of the thermostats on the UD Mobile interface shows blanks for all of the values. eISY also shows one of the devices with an "exclamation point" and no values. I can still see them in Apple Home and in the Meross app and responding properly.

My question is what is the proper steps to solve this? Can I just delete the thermostat from eISY and UD Mobile and re-add it? Do I have to clear a cache or other marker in the software that will prevent it from adding again? I know the universal devices matter is still beta, so I want make sure I do things right and don't lock my devices out of this environment.

Any suggestions?

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

20 minutes ago, oberkc said:

Unfortunately, based on my experience so far, adding matter devices to Alexa/Google/Apple/EISY only to find them losing connection later, then gaining it back, then losing it again, is not uncommon. This happens to me regularly and not just with the EISY. This morning, for example, one of the devices I added yesterday lost connection with Alexa.

Sometimes I find that trying to turn on/off the device from one of the hubs will re-establish communication. Sometimes, power cycling the non-responding device can work. I have had some matter devices simply drop wifi connection. Sometimes, nothing works besides deleting the device everywhere, factory resetting the device, then re-adding.

Still, it seems as if matter is making progress, if a bit slowly.

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.

19 hours ago, Javi said:

Most of eisy's Matter issues in the past were related to adding devices or adding controls/properties

I definitely experienced some of this.

19 hours ago, Javi said:

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

This has NOT been my experience. Yesterday evening, and not for the first time, a matter (wifi) device added three days ago stopped responding in all hubs (EISY, echo, google). The matter device (Govee, FWIW) remained connected to wifi and I could control it via its native app and its "works with Alexa" integration. Another Govee matter device continued to work (but for how long we will see). No...for me, other matter connection issues are NOT usually related to "dropped wifi networks".

5 hours ago, oberkc said:

This has NOT been my experience. Yesterday evening, and not for the first time, a matter (wifi) device added three days ago stopped responding in all hubs (EISY, echo, google). The matter device (Govee, FWIW) remained connected to wifi and I could control it via its native app and its "works with Alexa" integration. Another Govee matter device continued to work (but for how long we will see). No...for me, other matter connection issues are NOT usually related to "dropped wifi networks".

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.

9 hours ago, Javi said:

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.

That would make sense in isolation. Unfortunately for me, this was just the latest example of the weird and unreliable behavior of matter devices. (Even stranger, the next day, this device began working again.) This problem has occurred with all four of my matter devices, across three different brands (Govee, Nanoleaf, and Cync.) This is not a problem I associate as being caused by the EISY, but it is a problem that makes it hard for me to recommend matter to anyone at this point. I have spent far too many hours trying to make matter work for me and I will not be buying any more matter devices until I have some confidence these problems are solved.

Thanks for your thoughts, but I believe I have hijacked this thread too much already. If something changes where I think UD can help, I will get back to you.