ZMatter Zwave board not responding - Polisy

[EJones01]

I've opened a case but I suspect they are busy as its been two days and no reply. I installed my ZMatter board in my Polisy and after a day of fing around and deleting and readding my ZWave devices got it all working great. Two days later I rebooted Polisy(due to an issue with AVremote Node) and the ZMatter board now is not found. I shutdown and reseated it but still nothing. It worked fine for two days so not sure what to do now?

Elapsed 00:00:06.278 : Loading Variables
Elapsed 00:00:06.503 : Loading Node Definitions
Elapsed 00:00:06.775 : Loading Nodes
Elapsed 00:00:06.847 : Creating Widgets
Elapsed 00:00:08.675 : Creating Widgets Complete
Tue 01/31/2023 04:40:11 PM : Starting Subscription
Tue 01/31/2023 04:40:11 PM : Completing initialization
Tue 01/31/2023 04:40:11 PM : Refreshing Status
Tue 01/31/2023 04:40:11 PM : Refreshing Views
Tue 01/31/2023 04:40:12 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Serial data 16 bytes [011C00040008129F032B00DF59AF23AC]
Tue 01/31/2023 04:40:12 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Serial data 14 bytes [1488BC32CCA6627027BB00010318]
Tue 01/31/2023 04:40:12 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] ACK [011C00040008129F032B00DF59AF23AC1488BC32CCA6627027BB00010318]
Tue 01/31/2023 04:40:12 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial data
Tue 01/31/2023 04:40:13 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Clearing serial data (60 bytes) [011C00040008129F032C00EC613D07DB]
Tue 01/31/2023 04:40:13 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Requesting device information
Tue 01/31/2023 04:40:14 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Serial data 1 bytes [18]
Tue 01/31/2023 04:40:15 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Serial data 16 bytes [011C00040008129F032C00EC613D07DB]
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Serial data 14 bytes [C6F463787708841668BB00010334]
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] ACK [011C00040008129F032C00EC613D07DBC6F463787708841668BB00010334]
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial data
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Is not ZMatter Z-Wave
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU1] - Not our port
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] seqNo=4 isRemoved=False
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Start ZMatter Z-Wave port detection
Tue 01/31/2023 04:40:18 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:20 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:22 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:23 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:26 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:27 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:30 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:31 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:34 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:35 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:38 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:39 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:42 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:43 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:46 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:47 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:50 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:51 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:54 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Requesting device information
Tue 01/31/2023 04:40:55 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] No serial data
Tue 01/31/2023 04:40:56 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Is not ZMatter Z-Wave
Tue 01/31/2023 04:40:56 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] - Not our port
Tue 01/31/2023 04:40:56 PM : [USB PORTS][ZMatterZWave] initializePort - Not found, new seqnum=4
Tue 01/31/2023 04:40:56 PM : [USB PORTS] ZMatterZWave - setSeqNum(  4 ) was 0

Tue 01/31/2023 04:40:56 PM : [USB PORTS] initializePort for Insteon (seqNum=0)
Tue 01/31/2023 04:40:56 PM : [USB PORTS] Refresh ports
Tue 01/31/2023 04:40:56 PM : [USB PORTS] .. refresh port [/dev/ttyu0] ix=0
Tue 01/31/2023 04:40:56 PM : [USB PORTS] .. refresh port [/dev/ttyU0] ix=1
Tue 01/31/2023 04:40:56 PM : [USB PORTS] .. refresh port [/dev/ttyU1] ix=2
Tue 01/31/2023 04:40:56 PM : [USB PORTS] .. refresh port [/dev/ttyU2] ix=3
Tue 01/31/2023 04:40:56 PM : [USB PORTS] ... initializePort for Insteon .. numPortEntries=4
Tue 01/31/2023 04:40:56 PM : [USB PORTS][Insteon] initializePort [/dev/ttyu0] seqNo=1 isRemoved=False
 

Edited February 1, 2023 by EJones01

[gviliunas]

Hi @EJones01,

I was seeing a similar problem at reboot. When polisy boots, it asks the ZMatter board for an ID string. In my case, I had several very chatty z-wave devices that were sending data at < 1 second intervals. These were somehow confusing ZMatter and it wasn't responding to Polisy correctly.  I would see errors like the ones I see in your log:

Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial data
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Is not ZMatter Z-Wave
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU1] - Not our port
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] seqNo=4 isRemoved=False
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Start ZMatter Z-Wave port detection

Working with UDI, Chris recommended that I unplug some of the chatty devices. I did this and was able to boot. Ths allowed me to boot but the final solution, for me once the system was up, was to change parameters to reduce the frequency that some smart plugs were reporting energy usage. After doing this, I can reboot without problems. Hopefully your problem has a similar cause.

Good luck in getting your system working again.

Edited February 1, 2023 by gviliunas

[EJones01]

12 hours ago, gviliunas said:

Hi @EJones01,

I was seeing a similar problem at reboot. When polisy boots, it asks the ZMatter board for an ID string. In my case, I had several very chatty z-wave devices that were sending data at < 1 second intervals. These were somehow confusing ZMatter and it wasn't responding to Polisy correctly.  I would see errors like the ones I see in your log:

Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial data
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Is not ZMatter Z-Wave
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU1] - Not our port
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] seqNo=4 isRemoved=False
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Start ZMatter Z-Wave port detection

Working with UDI, Chris recommended that I unplug some of the chatty devices. I did this and was able to boot. Ths allowed me to boot but the final solution, for me once the system was up, was to change parameters to reduce the frequency that some smart plugs were reporting energy usage. After doing this, I can reboot without problems. Hopefully your problem has a similar cause.

Good luck in getting your system working again.

OMG...this was it!  I have a multi sensor that is set to read light level at 5 sec intervals. I have to say though this was like this with the USB dongle and worked OK, so is a bug in the new software. Thanks !!!

[gviliunas]

Hmmm Chris had said that sub-1 second reporting intervals might be a problem. I would have thought that 5 sec would be okay. In any event, once Polisy is up, you can plug that multi sensor back in any your system should run fine.

[brians]

13 hours ago, gviliunas said:

Hi @EJones01,

I was seeing a similar problem at reboot. When polisy boots, it asks the ZMatter board for an ID string. In my case, I had several very chatty z-wave devices that were sending data at < 1 second intervals. These were somehow confusing ZMatter and it wasn't responding to Polisy correctly.  I would see errors like the ones I see in your log:

Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial data
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Is not ZMatter Z-Wave
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU1] - Not our port
Tue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] seqNo=4 isRemoved=False
Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Start ZMatter Z-Wave port detection

Working with UDI, Chris recommended that I unplug some of the chatty devices. I did this and was able to boot. Ths allowed me to boot but the final solution, for me once the system was up, was to change parameters to reduce the frequency that some smart plugs were reporting energy usage. After doing this, I can reboot without problems. Hopefully your problem has a similar cause.

Good luck in getting your system working again.

What were the models of these plugs?

I have had issues with a Zen25 when I was using old Zooz USB dongle, it would flood the network and kill ZWave. This is actually a common problem with this particular device discussed on other forums/hubs, but Zooz is "unable to reproduce" in their lab. The solution seems to be decreasing the frequency or stopping the energy reporting entirely. I have not bothered to hook mine up again since ZMatter but may so eventually.

 

[EJones01]

Its the Aeotec Tri Sensor (but all there sensors will be the same) They don't come from factory like this. I changed it to report more often as I needed to know the light level all the time to avoid another automation failing. 

I have received help from UD now who helped disable looking for the port again on boot, So it now boots Ok even with this device plugged in.

[peterathans]

Curious, did UD indicate that this is a problem that can be fixed on their end, by updating the ZMatter firmware?  Just wondering if this was a one-off fix for your particular case or if they've acknowledged an issue that can affect their entire user base?

[EJones01]

On 2/1/2023 at 2:43 PM, peterathans said:

Curious, did UD indicate that this is a problem that can be fixed on their end, by updating the ZMatter firmware?  Just wondering if this was a one-off fix for your particular case or if they've acknowledged an issue that can affect their entire user base?

I'm not sure....but they do know about it, and I wasn't the first to talk to them about it...so I presume if they can do something they will.