Too many strange abnormal disconnections

General Discussion
41

From the screenshots, it looks like your zigbee network is fine.
LQI 255 is excelent, RSSI in a range -60 to -72 is not great, but fair.
There is some packet loss on the network, but it is not major.
And finally, your other zigbee devices work fine.
So we probably can eliminate connectivity issues between the hub and the cloud.

The devices might show offline for multiple reasons.

  1. The device does not send periodic messages
  2. The device sends periodic messages, but the hub expects them in shorter intervals
  3. The messages from device to hub are lost or corrupted (not likely in your case)
  4. Connectivity issues between the hub and the cloud (not likely in your case)
  5. The messages are received by the hub, but the platform is not notified (this is DTH specific)
    If you were using the same DTH without any issues before we can probably eliminate this one

Now, if I understand correctly, the switches rejoin as ‘Thing’ and you need to select the correct DTH manually. This might cause the device misconfiguration.

So, let’s see whether the devices are actually not responding or it is only a platform that thinks that they are offline.
I suggest to try the following:

  1. Select the device that shows offline and is using DTH
  2. Open live logging in IDE
  3. Press a physical switch
  4. See wether there are any messages in the live logging
  5. See whether the devices status is updated in the ST app
  6. Repeat 3-5 several times if device is not shown online
  7. Post live log here
42

Thank you also for your interest.
So now on 12 vimar 11 They are visible from the ide, only 2 with DH and 9 vith edge.
Maybe to do the test you say, I should delete the edge devices again and try everything again in DH what do you think?
However, I have a doubt. If I try to log in from IDE, I don’t see all zigbee devices connected directly to the hub locally. Only one of 2 my vimar with DH i see in the log.
I post the log after trying to turn it on from the App (it does not work, sometimes yes, now no. I’m away from home)
The other device works well now(it’s the only one) But I don’t see in the log ide.

This is the log of the device connect but not work from the app:

Screenshot_2022-02-07-09-58-02-14
Screenshot_2022-02-07-09-58-02-141080×2788 182 KB

Now I deleted all the Vimar with edge and deleted the driver back to DH to get a more complete view from IDE.
I will try to reset each device before connecting it again.

43

@ygerlovin I copied the log of the only vimar that appears in the logs of the ide. Something wrong seems to be there, but I don’t know what:

Logs

Clear

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:37: debug [raw:0104 0006 0A 01 0000 00 778B 00 00 0000 07 01 00, profileId:0104, clusterId:0006, sourceEndpoint:0A, destinationEndpoint:01, options:0000, messageType:00, dni:778B, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:6, commandInt:7]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:37: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0006 0A 01 0000 00 778B 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:37: debug description is catchall: 0104 0006 0A 01 0000 00 778B 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:35: debug [raw:0000 8021 00 00 0000 00 778B 00 00 0000 00 00 5100, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:778B, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[51, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:35: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 778B 00 00 0000 00 00 5100

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:35: debug description is catchall: 0000 8021 00 00 0000 00 778B 00 00 0000 00 00 5100

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:32: debug Configuring Reporting and Bindings.

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:20: debug [raw:B1C50A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:B1C5, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:20: warn DID NOT PARSE MESSAGE for description : read attr - raw: B1C50A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: B1C5, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:20: debug description is read attr - raw: B1C50A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: B1C5, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: debug [raw:B1C50A000014040000420556696D6172, dni:B1C5, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: warn DID NOT PARSE MESSAGE for description : read attr - raw: B1C50A000014040000420556696D6172, dni: B1C5, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: debug description is read attr - raw: B1C50A000014040000420556696D6172, dni: B1C5, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: debug [raw:B1C50A00000A0100002001, dni:B1C5, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: warn DID NOT PARSE MESSAGE for description : read attr - raw: B1C50A00000A0100002001, dni: B1C5, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:19: debug description is read attr - raw: B1C50A00000A0100002001, dni: B1C5, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:18: debug Configuring Reporting and Bindings.

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:08: debug [raw:86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:86FE, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:08: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 86FE, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:08: debug description is read attr - raw: 86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 86FE, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug [raw:0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:86FE, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[37, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug description is catchall: 0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug [raw:86FE0A000014040000420556696D6172, dni:86FE, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A000014040000420556696D6172, dni: 86FE, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug description is read attr - raw: 86FE0A000014040000420556696D6172, dni: 86FE, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug [raw:0104 0006 0A 01 0000 00 86FE 00 00 0000 07 01 00, profileId:0104, clusterId:0006, sourceEndpoint:0A, destinationEndpoint:01, options:0000, messageType:00, dni:86FE, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:6, commandInt:7]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0006 0A 01 0000 00 86FE 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:07: debug description is catchall: 0104 0006 0A 01 0000 00 86FE 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:06: debug [raw:86FE0A00000A0100002001, dni:86FE, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:06: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A00000A0100002001, dni: 86FE, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:06: debug description is read attr - raw: 86FE0A00000A0100002001, dni: 86FE, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:05: debug [raw:86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:86FE, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:05: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 86FE, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:05: debug description is read attr - raw: 86FE0A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 86FE, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: debug [raw:0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:86FE, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[37, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: debug description is catchall: 0000 8021 00 00 0000 00 86FE 00 00 0000 00 00 3700

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: debug [raw:86FE0A000014040000420556696D6172, dni:86FE, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A000014040000420556696D6172, dni: 86FE, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:04: debug description is read attr - raw: 86FE0A000014040000420556696D6172, dni: 86FE, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:03: debug [raw:86FE0A00000A0100002001, dni:86FE, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:03: warn DID NOT PARSE MESSAGE for description : read attr - raw: 86FE0A00000A0100002001, dni: 86FE, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:41:03: debug description is read attr - raw: 86FE0A00000A0100002001, dni: 86FE, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:55: debug [raw:0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00, profileId:0104, clusterId:0006, sourceEndpoint:0A, destinationEndpoint:01, options:0000, messageType:00, dni:2F28, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:6, commandInt:7]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:55: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:55: debug description is catchall: 0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:49: debug [raw:0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00, profileId:0104, clusterId:0006, sourceEndpoint:0A, destinationEndpoint:01, options:0000, messageType:00, dni:2F28, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:6, commandInt:7]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:49: warn DID NOT PARSE MESSAGE for description : catchall: 0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:49: debug description is catchall: 0104 0006 0A 01 0000 00 2F28 00 00 0000 07 01 00

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: debug [raw:2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:2F28, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 2F28, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: debug description is read attr - raw: 2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 2F28, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: debug [raw:0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:2F28, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[24, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:48: debug description is catchall: 0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:47: debug [raw:2F280A000014040000420556696D6172, dni:2F28, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:47: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A000014040000420556696D6172, dni: 2F28, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:47: debug description is read attr - raw: 2F280A000014040000420556696D6172, dni: 2F28, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:46: debug [raw:2F280A00000A0100002001, dni:2F28, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:46: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A00000A0100002001, dni: 2F28, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:46: debug description is read attr - raw: 2F280A00000A0100002001, dni: 2F28, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: debug [raw:2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:2F28, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 2F28, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: debug description is read attr - raw: 2F280A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 2F28, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: debug [raw:0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:2F28, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[24, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:45: debug description is catchall: 0000 8021 00 00 0000 00 2F28 00 00 0000 00 00 2400

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:44: debug [raw:2F280A000014040000420556696D6172, dni:2F28, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:44: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A000014040000420556696D6172, dni: 2F28, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:44: debug description is read attr - raw: 2F280A000014040000420556696D6172, dni: 2F28, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:43: debug [raw:2F280A00000A0100002001, dni:2F28, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:43: warn DID NOT PARSE MESSAGE for description : read attr - raw: 2F280A00000A0100002001, dni: 2F28, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:43: debug description is read attr - raw: 2F280A00000A0100002001, dni: 2F28, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:43: debug Configuring Reporting and Bindings.

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:33: debug [raw:0000 8021 00 00 0000 00 9321 00 00 0000 00 00 1300, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:9321, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[13, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:33: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 9321 00 00 0000 00 00 1300

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:33: debug description is catchall: 0000 8021 00 00 0000 00 9321 00 00 0000 00 00 1300

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:32: debug [raw:93210A00000A0100002001, dni:9321, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:32: warn DID NOT PARSE MESSAGE for description : read attr - raw: 93210A00000A0100002001, dni: 9321, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:32: debug description is read attr - raw: 93210A00000A0100002001, dni: 9321, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:31: debug description is catchall: 0104 0006 0A 01 0000 00 9321 00 00 0000 01 01 0000001001

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:31: debug [raw:93210A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:9321, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:31: warn DID NOT PARSE MESSAGE for description : read attr - raw: 93210A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 9321, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:31: debug description is read attr - raw: 93210A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 9321, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:31: debug Configuring Reporting and Bindings.

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: debug [raw:27E70A00000A0100002001, dni:27E7, endpoint:0A, cluster:0000, size:10, attrId:0001, result:success, encoding:20, value:01, isValidForDataType:true, clusterInt:0, attrInt:1]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: warn DID NOT PARSE MESSAGE for description : read attr - raw: 27E70A00000A0100002001, dni: 27E7, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: debug description is read attr - raw: 27E70A00000A0100002001, dni: 27E7, endpoint: 0A, cluster: 0000, size: 10, attrId: 0001, result: success, encoding: 20, value: 01

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: debug [raw:0000 8021 00 00 0000 00 27E7 00 00 0000 00 00 1300, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:27E7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[13, 00], clusterInt:32801, commandInt:0]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 27E7 00 00 0000 00 00 1300

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:27: debug description is catchall: 0000 8021 00 00 0000 00 27E7 00 00 0000 00 00 1300

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:26: debug [raw:27E70A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni:27E7, endpoint:0A, cluster:0000, size:46, attrId:0005, result:success, encoding:42, value:4F6E5F4F66665F5377697463685F76312E30, isValidForDataType:true, clusterInt:0, attrInt:5]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:26: warn DID NOT PARSE MESSAGE for description : read attr - raw: 27E70A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 27E7, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:26: debug description is read attr - raw: 27E70A00002E05000042124F6E5F4F66665F5377697463685F76312E30, dni: 27E7, endpoint: 0A, cluster: 0000, size: 46, attrId: 0005, result: success, encoding: 42, value: 4F6E5F4F66665F5377697463685F76312E30

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:25: debug [raw:27E70A000014040000420556696D6172, dni:27E7, endpoint:0A, cluster:0000, size:20, attrId:0004, result:success, encoding:42, value:56696D6172, isValidForDataType:true, clusterInt:0, attrInt:4]

2915f278-922b-44ae-a94c-9edb9977c7c2 11:40:25: warn DID NOT PARSE MESSAGE for description : read attr - raw: 27E70A000014040000420556696D6172, dni: 27E7, endpoint: 0A, cluster: 0000, size: 20, attrId: 0004, result: success, encoding: 42, value: 56696D6172

44

Which model exactly do you have? Does it have Bluetooth also? If you say many other users on the Italian ST Facebook group are having similar issues with Vimar, I fear you could be fighting a losing battle. @sulisenator

1 Like
45

The model is vimar 14592
Your question about Bluetooth gave me an idea. I try to change them all to bluetooth and try to add them in zigbee one at a time.

I did a survey on the Italian Facebook group, only 7 people reported this problem, but I don’t know if actually I did a survey on the Italian Facebook group, only 7 people reported this problem, but I don’t know if it’s actually the same problem :man_shrugging:t2:. Thanks, I will continue my tests, even now the new devices inserted disconnect at random even if connected directly to the hub.

46

Apparently within the first 5 minutes of powering on you need to connect to the device via Bluetooth with the “View” app, that enables a “conversion” to Zigbee software on the device.

"CONFIGURATION IN ZIGBEE.
Follow the procedure above from points 1 to 3.
Associate the 2-way switch directly with Amazon Echo Plus, Echo Show or Echo Studio.

  1. Press the button on the 2-way switch until the LED flashes. Download the Zigbee software
    onto the device using the View Wireless App (see the View Wireless App manual).
    To update the software on the device, the procedure is the same.
  2. After conversion to Zigbee technology (or the software update), the 2-way switch automatically
    goes into pairing mode so that it can be recognised by the Amazon device within 5 minutes.
    If the 2-way switch is not in pairing mode, cut off the power supply and restore it after a few
    seconds.
  3. Associate the 2-way switch with Amazon Echo Plus, Echo Show or Echo Studio according to
    the procedure envisaged by the voice assistant (see the Amazon documentation)."

I admire your perseverance.

47

I had too a disconnection of a Vimar device, after 1 year or so of stable functioning, I re added it, it dropped againa fter 1 month. I removed the device from ST app, because I hadn’t the time to run more tests, then after the last hub update (I don’t know if that is related) the device showed up online again without me searching for it. Werid.

Just yesterday though anothe zigbee device, a silvanya/osram sensor, which has been working for several years, dropped. I re-added it but it was unfortunately paired with the wrong driver, I removed it and after unistalling the driver I tried to re add it, with no luck, the device wouldn’t pair anymore.

There might be some issues with zigbee on the hub side, I can’t say for sure,

1 Like
48

Yes, I know by heart the procedure, done more than 100 times now :rofl::roll_eyes:.
Before I meant to say that I change to bluetooth everyone, so as not to have wandering zigbee devices, maybe they are the problem, who knows.

Conosco @sulisenator :hugs: We had talked on FB about this problem.

49

@Diegocampy

If you are going to reconnect with DTH, if you want, tell me the complete fingerprint and I will modify the DTH so that they are installed and configured correctly.

1 Like
50

@Diegocampy,

What you see in the log you sent from the device with DTH is that it is constantly reconnecting to the network and constantly obtaining a new DNI.
It’s constantly rejoint, you should disable unsecure rejoint in the hub options in the app or IDE.

That way when you uninstall the device it will re-pair only when you add device in the app

51

Hi @Diegocampy

The log shows the DTH is unable to parse the messages. It is not necessary a problem, but may indicate an issue.
Are you sure you are using the exactly same DTH that previously was working fine?
Have you tried to turn on/off the physical switch?
I couldn’t find indication for this in the log.

DTH and edge drivers should not interfere with each other. However, it could be an issue. If you decide to delete all devices that are using edge driver, please remember to also uninstall edge driver and reboot the hub.

52

Hi @Mariano_Colmenarejo ,

How would you know that? There are multiple DNIs in the log, how do you know it is the same device or may be there many different devices that try to reconnect?

53

This is the device Id and it is always the same.
Device get a different DNI every time it do a zigbee rejoint on the network.

dni:778B,
dni: B1C5
dni:86FE
dni:2F28
dni: 9321
dni: 27E7

If we see the events of the Hub, the rejoint events of the device would be seen

54

@Mariano_Colmenarejo , cool, thank you very much for explanation

1 Like
55

I can never thank you enough for your attempts to help! Before answering your questions, let me update you on what I did today after my last message this morning:

  • i deleted all vimar devices with EDGE drive

  • I waited and saw that a “thing” device appeared every few minutes.

  • When it appeared, I renamed it to “. Thing” from app and then from ide I went to change the DH with “zigbee switch”.

  • I checked that everything was working and continued one at a time, but without ever having searched for devices, they appeared by themselves.

  • I thought about switching a few devices to Bluetooth to eliminate potential zigbee devices that might have been confusing. (my idea, probably wrong) in the end I only did 3 and not all of them

  • no new devices appeared and I had 7 working

  • I changed from zigbee to bluetooth and from bluetooth to zigbee, 2 devices (one at a time) to try to add them manually. The devices did not appear immediately, but after a few minutes. I then changed my name to .thing and then changed DH, first to one and then to the other, resulting in 9 working devices.
    (until now, all devices had a direct connection to the Hub or no route traced by the IDE)

  • the problems begin, after a few minutes, the penultimate device added (very close to the hub, only 5m without walls) has disconnected.

Now I stopped because I don’t know whether to try to delete it, or whether to delete the last one I added, or I don’t know what else to do, but to try hubitat or home assistant :frowning:

I really appreciate your help, yes I’m trying again with DH just to be able to check from IDE what is happening and where each device is connected. For the fingerprint, I have no idea what to do. I just think, however, that with a modified DH, I would no longer have local performance right? but maybe you recommend it only for this test phase?

in this way?

image
image1117×858 56.5 KB

yes, the same DTH
yes I try to turn on/off but no change in the log.
I don’t understand why only some devices and not all appear in the log. Now I have been trying to keep the log open for several minutes, but only one of all the vimars currently in use is displayed

56

Yes, or from app

Screenshot_20220207-234443
Screenshot_20220207-2344431023×2048 148 KB

My experience with modified stock DTH is that if you keep the same name as the stock DTH it will work as local and automations too

1 Like
57

I would now add that since a device was disconnected, the problems of switching on and off from the app also started with 3 other vimar devices. I deleted the disconnected device, the problems with the other devices remain

58

@Diegocampy,
Pass me the fingerprint and if you want you can use modified DTH, I’m going to sleep, it’s too late

1 Like
60

I don’t know where to read it

61

In IDE, device RAW data

fingerprints-1
fingerprints-12282×1394 132 KB