Unable to add presence sensor

Developer Programs Support
1

Hi,

I have three SmartThings old style presence sensors all of which have been connected and working without issue. Removed two of them due to lack of use a year ago +/- with the third remaining in use.

Came to reconnect the two unused ones today after resetting and the hub (v2 UK) is stubbornly refusing to find either of them - after many attempts!

The 3rd remains connected and fully functioning. Is this due to ongoing changes and these devices are no longer supported for new pairings?

Any ideas would be appreciated…

2

Model number?

3

Did you try pairing them with them sitting on top of your hub?

4

@jkp good question my apologies, all are PGC418-C (STSS-PRES-001)

@Paul_Oliver yes and at varying distances…

5

any chance the battery might have drained on both?
possible you did not reset them properly?

try to add > ST app > Add Device > choose Scan

6

Tried scanning as well as specific device route and tried two sets of new batteries. Multiple resets too so unlikely they all failed…

7

I had several of those tags and they used to work well for me, though they were never easy to pair. A while back I had cause to change my Zigbee channel and only one or two changed automatically to match and I spent hours trying to pair the others. Before I could finish the job I had to move the channel again and things were even worse. I decided enough was enough and chucked the lot.

1 Like
8

Is there any way to show a CLI log only with scan proccess?
To understand if the new device is communicating with the hub, specially when the device do not appear in the app.

I have a zigbee button that was sync in my ST, and now I am not able to sync again to add with Edge driver.

9

The logs that we can see in through the CLI only show the discovery process of a device that is supported by a driver, it doesn’t include those from DTH.
Also, the part of scanning to see if a match was found isn’t included. If you don’t see any logs from the driver you expect to install the device when you hit “scan nearby”, it means the device isn’t supported.

Those logs are activated using this command:

smartthings edge:drivers:logcat --hub-address=x.x.x.x --all

Remember to replace x.x.x.x with the actual Hub’s IP Address which can be found in the IDE (“My Hubs” menu > Hub details) or your router’s configuration page.
The flag --all allows you to see the logs of all the drivers installed, if you don’t add it, the CLI will ask you to select one.

Also, a good indicator of the interaction with the Hub is the LED included in the physical device. In their corresponding manual, it will list how will the LED behave when it is in “pairing mode”, when it “paired”, or when it stopped the process because it wasn’t discovered.

1 Like
10

Thanks @nayelyz … this way I know. But do not enable any kind of “grep”, correct?
Also, not synced devices (found but not synced) are not available in this log.
I was looking for something “deeper” in hub+device communication.

11

What do you mean by “found but not synced”, when the device is found only as a “thing”?
There are drivers that will discover any device so it gets added as a thing (Zigbee-Thing and Z-Wave Switch), those are there to allow you to see the device’s fingerprints and supported clusters so you can develop your own driver or add the fingerprints to an existing one.
They are not part of the production drivers that are installed automatically when pairing a device so, you need to install them from the official channel invitation)

Those are the only logs we can access about the device pairing with a driver.
The internal logs can be accessed by the team in case there’s an issue.

1 Like
12

I am looking a way to debug when the device blinks as it had the first connection with the hub, but did not appeared even as Thing (nothing appears). But I understand that this is not available.

Please @nayelyz … another question… I have another device that Model and Manufacteur are blank (cloud image), but “Ep” are available. Is there any way to force an edge driver?

13

Are you referring to a driver developed by @Mariano_Colmenarejo? The official drivers don’t show those values in the app, only the driver logs, after the driver’s init config, you will see something like:

Manufacturer: 0x0086 Product Type: 0x0102 Product ID: 0x0059
        [0]: VERSION, MANUFACTURER_SPECIFIC, SENSOR_BINARY, BATTERY, WAKE_UP, CONFIGURATION, ASSOCIATION, ASSOCIATION_GRP_INFO, NOTIFICATION, FIRMWARE_UPDATE_MD, POWERLEVEL, HAIL, ZWAVEPLUS_INFO, SECURITY, DEVICE_RESET_LOCALLY

By “forcing a driver”, do you mean assigning one to control the device? You can change the driver to which the device originally paired, but, the other driver must include the device’s fingerprints. Otherwise, the driver won’t appear in the “select a different driver” option in the app.

14

Are you referring to a driver developed by @Mariano_Colmenarejo? The official drivers don’t show those values in the app, only the driver logs, after the driver’s init config, you will see something like:

In his edge driver and in Groovy… I had the same before.

By “forcing a driver”, do you mean assigning one to control the device? You can change the driver to which the device originally paired, but, the other driver must include the device’s fingerprints. Otherwise, the driver won’t appear in the “select a different driver” option in the app.

By “forcing a driver” means “to able to do like in Groovy, selecting thirdparty drivers and to understand how the device reacts”. I was trying to force some drivers to find quickly find a way to enable a non compatible device, and increase new drivers, without need to “recreate the wheel”.

But my question is…
Is there any way to add a device to Edge driver without Model and Manufacteur?
Thanks!

15

No, you need to add the fingerprints to the driver, or as @Mariano_Colmenarejo mentioned below, you can set generic fingerprints but he’s right about their behavior.
If it’s a Z-Wave device, you can find the device info here:
https://products.z-wavealliance.org/products/
You just need to search it by brand and model

If it’s a Zigbee device, sometimes there are pages on the web where other users have mentioned them or their technical sheet.

So, if I understand correctly, you cannot see the device info even in the logs when you pair it? that’s really odd…Can you share the brand and model?

16

Hi @allmac
I’m sure @nayelyz will give you an answer, but I’m going to give you my humble opinion based on the experience of these months of Beta drivers.

The problem is no longer that you manage to match device with the driver, that you can also do pairing with the device clusters. You can see examples in the fingerprints.yml of Smartthings GitHub drivers.

But need to select groups of clusters and also assign profiles from those that the driver has or create specific ones.

This has its problems, since devices that share some clusters will be paired to the same profile even if they are very different devices.

Then there is a difference with device configuration:

  • With DTH, if you change the DTH, a new configuration of the device is performed and that will make it work correctly if it is the appropriate DTH
  • With Edge driver, if you change the driver, the Configure lifecycle is not executed by default and therefore the device will not be configured to work with the new profile of the new driver.

I run Configure lifecycle manually in my drivers when change the driver (driverSwitched lifecycle), to make sure that if someone chooses to change to my driver and their device is compatible, it is configured correctly, but this does not happen in most stock drivers.

Therefore, I believe that forcing any device to be paired with any driver does not help and can create problems for users.

2 Likes
17

@nayelyz

The device that appears without Model and Manuf. is this one:
Model: ZYCT-202
Vendor: Trust

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/ZYCT-202.md

Trust ZYCT-202 setting up dimming via zigbee2mqtt - #8 by xaviml - Zigbee - Home Assistant Community

Trust / KaKu ZYCT-202 [Working] · Issue #222 · stas-demydiuk/domoticz-zigbee2mqtt-plugin · GitHub

Following I am sending the logcat using @Mariano_Colmenarejo Zigbee Thing driver.

Device removed:

2022-08-03T23:13:30.277567628+00:00 TRACE Zigbee Thing Mc  Received event with handler device_lifecycle
2022-08-03T23:13:30.282751586+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: c00c032c-adc4-46b4-8976-c974cce399e1 [0x9DDD] (Zigbee Thing)> received lifecycle event: removed
2022-08-03T23:13:30.293415711+00:00 TRACE Zigbee Thing Mc  <ZigbeeDevice: c00c032c-adc4-46b4-8976-c974cce399e1 [0x9DDD] (Zigbee Thing)> received unhandled lifecycle event: removed
2022-08-03T23:13:30.299265378+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:13:30.307778586+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:13:38.470609308+00:00 DEBUG Zigbee Thing Mc  driver device thread event handled

Device added:

2022-08-03T23:18:59.401078064+00:00 TRACE Zigbee Thing Mc  Received event with handler device_lifecycle
2022-08-03T23:18:59.413952856+00:00 TRACE Zigbee Thing Mc  Zigbee Device: 34e2e786-10a2-4923-b24d-2e1b456c5863
Manufacturer:  Model: 
	[1]: Basic, Groups, Identify, OnOff, Level, TouchlinkCommissioning	[2]: TouchlinkCommissioning
2022-08-03T23:18:59.419446668+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received lifecycle event: added
2022-08-03T23:18:59.430249522+00:00 TRACE Zigbee Thing Mc  Received event with handler device_lifecycle
2022-08-03T23:18:59.434336210+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received lifecycle event: doConfigure
2022-08-03T23:18:59.441890168+00:00 TRACE Zigbee Thing Mc  Found DeviceLifecycleDispatcher handler in zigbee_thing
2022-08-03T23:18:59.446321439+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"manufacturer","capability_id":"legendabsolute60149.manufacturer","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.525134731+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"model","capability_id":"legendabsolute60149.model","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.609058772+00:00 PRINT Zigbee Thing Mc  Server Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.630555689+00:00 PRINT Zigbee Thing Mc  Client Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.636731731+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"clustersInfo","capability_id":"legendabsolute60149.clustersInfo","component_id":"main","state":{"value":"<table style='font-size:60%'> <tbody><tr> <th align=left></th> <td><em style='color:Green;font-weight: bold;'> Server Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr><tr> <th align=left></th> <td><em style='color:Blue;font-weight: bold;'> Client Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr></tbody></table>"}}
2022-08-03T23:18:59.741220980+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:18:59.746381189+00:00 TRACE Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received unhandled lifecycle event: init
2022-08-03T23:18:59.750336314+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:18:59.754149189+00:00 TRACE Zigbee Thing Mc  Received event with handler capability
2022-08-03T23:18:59.764945522+00:00 TRACE Zigbee Thing Mc  Found DeviceLifecycleDispatcher handler in zigbee_thing
2022-08-03T23:18:59.769018210+00:00 TRACE Zigbee Thing Mc  Found CapabilityCommandDispatcher handler in zigbee_thing
2022-08-03T23:18:59.773091189+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"manufacturer","capability_id":"legendabsolute60149.manufacturer","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.784858043+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"model","capability_id":"legendabsolute60149.model","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.798337855+00:00 PRINT Zigbee Thing Mc  Server Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.802095960+00:00 PRINT Zigbee Thing Mc  Client Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.806657897+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"clustersInfo","capability_id":"legendabsolute60149.clustersInfo","component_id":"main","state":{"value":"<table style='font-size:60%'> <tbody><tr> <th align=left></th> <td><em style='color:Green;font-weight: bold;'> Server Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr><tr> <th align=left></th> <td><em style='color:Blue;font-weight: bold;'> Client Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr></tbody></table>"}}
2022-08-03T23:18:59.819981293+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:18:59.865294168+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:18:59.877293251+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","positional_args":{}}
2022-08-03T23:18:59.884247709+00:00 TRACE Zigbee Thing Mc  Found CapabilityCommandDispatcher handler in zigbee_thing
2022-08-03T23:18:59.889490855+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"manufacturer","capability_id":"legendabsolute60149.manufacturer","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.902145668+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"model","capability_id":"legendabsolute60149.model","component_id":"main","state":{"value":""}}
2022-08-03T23:18:59.918464314+00:00 PRINT Zigbee Thing Mc  Server Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.922557730+00:00 PRINT Zigbee Thing Mc  Client Clusters >>>	<b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR>
2022-08-03T23:18:59.927542043+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> emitting event: {"attribute_id":"clustersInfo","capability_id":"legendabsolute60149.clustersInfo","component_id":"main","state":{"value":"<table style='font-size:60%'> <tbody><tr> <th align=left></th> <td><em style='color:Green;font-weight: bold;'> Server Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr><tr> <th align=left></th> <td><em style='color:Blue;font-weight: bold;'> Client Clusters:</em></td></tr><tr> <th align=left></th> <td><b>Ep: </b>01={ 0000,0004,0003,0006,0008,1000 }<BR><b>Ep: </b>02={ 1000 }<BR></td></tr></tbody></table>"}}
2022-08-03T23:18:59.942109751+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:19:00.632354438+00:00 TRACE Zigbee Thing Mc  Received event with handler device_lifecycle
2022-08-03T23:19:00.640927771+00:00 INFO Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received lifecycle event: infoChanged
2022-08-03T23:19:00.653653938+00:00 TRACE Zigbee Thing Mc  <ZigbeeDevice: 34e2e786-10a2-4923-b24d-2e1b456c5863 [0x3200] (Zigbee Thing)> received unhandled lifecycle event: infoChanged
2022-08-03T23:19:00.657741417+00:00 DEBUG Zigbee Thing Mc  Zigbee Thing device thread event handled
2022-08-03T23:19:08.551699868+00:00 DEBUG Zigbee Thing Mc  driver device thread event handled

The most incredible are the empty fields

{"attribute_id":"manufacturer","capability_id":"legendabsolute60149.manufacturer","component_id":"main","state":{"value":""}}
{"attribute_id":"model","capability_id":"legendabsolute60149.model","component_id":"main","state":{"value":""}}
18

Hi!

Sorry for the delay. Following up on this, the team mentioned that, those values don’t appear because the info couldn’t be retrieved from it when the device was paired (this means the device didn’t send the values).

So, if we can’t retrieve that info, the device should pair with a generic fingerprint based on the supported clusters. For example, in the official repo and the Zigbee Switch there are some generic fingerprints that you can take as a reference.

The cluster IDs are included in the Edge reference and I included the ones you’d need based i yi¡ur

  - id: "ZYCT-202"
    deviceLabel: ZYCT-202
    clusters:
      server:
        - 0x0000 #Basic
        - 0x0003 #Identify
        - 0x0004 #Groups
        - 0x0006 #OnOff
        - 0x0008 #Level
        - 0x1000 #TouchlinkCommissioning
    deviceProfileName: profileName
1 Like
19

Thanks @nayelyz !!

1 Like