Zigbee device is not connected with edge driver even the model and manufacturer is exactly same as fingerprint

zigbee device is labeled as “Zigbee thing” after paring on hub.
when I check out the “zigbee thing” information, the model and manufacturer name was same as fingerprint.yml. when I watched the edge driver log, it never leave any log message but only zigbee thing driver left log that it received the model and manufacturer name.
is there anything I didn’t decide for my edge driver? model and manufacturer name is not enough for edge driver? Please help me about this. I have tested th this iis more than 1 week only for this issue but still the is no possibility..
the following is fingerprin.yml

fingerprints:

  • id: “SCIONIX SMS-107”
    deviceLabel: “SCIONIX SMS-107”
    manufacturer: “MAX Electronics”
    model: “SMS-107”
    deviceProfileName: “Multi-Sensor-000”

Try:

id: "MAX Electronics/SMS-107"

The id is usually “manuf/prod”.

The id is just a unique id for that fingerprint, it’s not used to match anything. Don’t ask me how I learned it :sweat_smile:

2 Likes

Thanks for your comment. I will try as your advice. Is this the reason why not being loaded my edge driver?

deviceProfileName is usually lowercase.

Is this the reason why not being loaded my edge driver?

Maybe the manufacturer is SCIONIX?

in the “zigbee thing” , model name is "SMS-107, Manufacturer is “MAX Electronics” and “SCIONIX” is brand name..thanks

fingerprints:

  • id: “MAX Electronics/SMS-107”
    deviceLabel: “SCIONIX SMS-107”
    manufacturer: “MAX Electronics”
    model: “SMS-107”
    deviceProfileName: “multi-sensor-000”

Fingerprint is modified as above but the result was same unfortunately..

Start the logging of the Zigbee Thing driver, add the device, post the output here.

Make sure to add ``` before and after, like this:

```
Paste
```

1 Like


model, manufacturer is correctly loaded

Before adding—

After adding–

Hub Driver–

Show us the logs.

Zigbee thing driver has following log

─────────────────────────────────────────────────────────────────────────

Driver Id Name

────────────────────────────────────────────────────────────────────────────
1 01976eca-e7ff-4d1b-91db-9c980ce668d7 Aqara Presence Sensor
2 c856a3fd-69ee-4478-a224-d7279b6d978f bose
3 9050ac53-358c-47a1-a927-9a70f5f28cee DEEPSMART KNX GATEWAY
4 4eb5b19a-7bbc-452f-859b-c6d7d857b2da Harman Luxury
5 7beb8bc2-8dfa-45c2-8fdb-7373d4597b12 JBL
────────────────────────────────────────────────────────────────────────────
6 1f03c136-a7be-409e-abaa-5da29cac75e3 Multi-Sensor SMS-107 Driver V016
7 cd898d81-6c27-4d27-a529-dfadc8caae5a Philips Hue
8 dbe192cb-f6a1-4369-a843-d1c42e5c91ba SamsungAudio
9 c21a6c77-872c-474e-be5b-5f6f11a240ef Sonos
10 d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b Wemo
────────────────────────────────────────────────────────────────────────────
11 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch
12 8bf71a5d-677b-4391-93c2-e76471f3d7eb Zigbee Thing
────────────────────────────────────────────────────────────────────────────
? Select a driver. 12
connecting… connected
2025-06-09T19:16:32.533779628+09:00 TRACE Zigbee Thing Setup driver zigbee_thing with lifecycle handlers:
DeviceLifecycleDispatcher: zigbee_thing
default_handlers:
doConfigure:
driverSwitched:
child_dispatchers:

2025-06-09T19:16:32.536322793+09:00 TRACE Zigbee Thing Setup driver zigbee_thing with Capability handlers:
CapabilityCommandDispatcher: zigbee_thing
default_handlers:
refresh:
refresh
child_dispatchers:

2025-06-09T19:16:32.538033122+09:00 INFO Zigbee Thing Created dispatcher [SecretDataDispatcher]zigbee_thing that had no handlers
2025-06-09T19:16:32.540373320+09:00 TRACE Zigbee Thing Setup driver zigbee_thing with Secret Data handlers:
SecretDataDispatcher: zigbee_thing
default_handlers:
child_dispatchers:

2025-06-09T19:16:32.542215902+09:00 TRACE Zigbee Thing Setup driver zigbee_thing with Zigbee handlers:
ZigbeeMessageDispatcher: zigbee_thing
default_handlers:
attr:
global:
cluster:
zdo:
child_dispatchers:

2025-06-09T19:16:32.602798441+09:00 TRACE Zigbee Thing Zigbee Device: db93b2bf-d7bb-4df5-8f8c-732eb49af349
Manufacturer: MAX Electronics Model: SMS-107
[1]: server: Basic, 0xFC10 | client
2025-06-09T19:16:32.604723785+09:00 DEBUG Zigbee Thing driver device thread event handled
2025-06-09T19:16:32.606990728+09:00 TRACE Zigbee Thing Received event with handler driver_lifecycle
2025-06-09T19:16:32.608550624+09:00 INFO Zigbee Thing received driver startupState: {“hub_zigbee_id”:“YO+r//4kjh0=”,“hub_node_id”:null,“hub_ipv4”:“192.168.0.74”}
2025-06-09T19:16:32.624058736+09:00 TRACE Zigbee Thing Received event with handler environment_info
2025-06-09T19:16:32.626428287+09:00 TRACE Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received unhandled lifecycle event: init
2025-06-09T19:16:32.628557514+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.630121038+09:00 TRACE Zigbee Thing Received event with handler environment_info
2025-06-09T19:16:32.645284841+09:00 INFO Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> generating doConfigure event for TYPED provisioning state
2025-06-09T19:16:32.648259789+09:00 TRACE Zigbee Thing Found DeviceLifecycleDispatcher handler in zigbee_thing
2025-06-09T19:16:32.650452850+09:00 TRACE Zigbee Thing Found CapabilityCommandDispatcher handler in zigbee_thing
2025-06-09T19:16:32.652184984+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.653869044+09:00 DEBUG Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> doConfigure callback did not fail, transitioning device to “PROVISIONED”
2025-06-09T19:16:32.655705705+09:00 TRACE Zigbee Thing Received event with handler device_lifecycle
2025-06-09T19:16:32.658274054+09:00 INFO Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received lifecycle event: added
2025-06-09T19:16:32.676273088+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.678038452+09:00 TRACE Zigbee Thing Received event with handler device_lifecycle
2025-06-09T19:16:32.679575917+09:00 INFO Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received lifecycle event: doConfigure
2025-06-09T19:16:32.687920464+09:00 TRACE Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received unhandled lifecycle event: added
2025-06-09T19:16:32.689523722+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.696225234+09:00 TRACE Zigbee Thing Found DeviceLifecycleDispatcher handler in zigbee_thing
2025-06-09T19:16:32.698621303+09:00 TRACE Zigbee Thing Found CapabilityCommandDispatcher handler in zigbee_thing
2025-06-09T19:16:32.701276416+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.702922327+09:00 DEBUG Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> doConfigure callback did not fail, transitioning device to “PROVISIONED”
2025-06-09T19:16:32.717677654+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled
2025-06-09T19:16:32.951769752+09:00 TRACE Zigbee Thing Received event with handler device_lifecycle
2025-06-09T19:16:32.954542358+09:00 INFO Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received lifecycle event: infoChanged
2025-06-09T19:16:32.959897656+09:00 TRACE Zigbee Thing <ZigbeeDevice: db93b2bf-d7bb-4df5-8f8c-732eb49af349 [0x05D5] (Zigbee Thing)> received unhandled lifecycle event: infoChanged
2025-06-09T19:16:32.961498037+09:00 DEBUG Zigbee Thing Zigbee Thing device thread event handled

Edge Driver log has nothing appeared as follow

───────────────────────────────────────────────────────────────────────────────────

Label Name Device Id

───────────────────────────────────────────────────────────────────────────────────
1 SmartThings Station SmartThings Station cdeac164-0bb7-429d-a98f-dbc363c17545
───────────────────────────────────────────────────────────────────────────────────
? Select a hub. 1
────────────────────────────────────────────────────────────────────────────

Driver Id Name

────────────────────────────────────────────────────────────────────────────
1 01976eca-e7ff-4d1b-91db-9c980ce668d7 Aqara Presence Sensor
2 c856a3fd-69ee-4478-a224-d7279b6d978f bose
3 9050ac53-358c-47a1-a927-9a70f5f28cee DEEPSMART KNX GATEWAY
4 4eb5b19a-7bbc-452f-859b-c6d7d857b2da Harman Luxury
5 7beb8bc2-8dfa-45c2-8fdb-7373d4597b12 JBL
────────────────────────────────────────────────────────────────────────────
6 1f03c136-a7be-409e-abaa-5da29cac75e3 Multi-Sensor SMS-107 Driver V016
7 cd898d81-6c27-4d27-a529-dfadc8caae5a Philips Hue
8 dbe192cb-f6a1-4369-a843-d1c42e5c91ba SamsungAudio
9 c21a6c77-872c-474e-be5b-5f6f11a240ef Sonos
10 d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b Wemo
────────────────────────────────────────────────────────────────────────────
11 f2e891c6-00cc-446c-9192-8ebda63d9898 Zigbee Switch
12 8bf71a5d-677b-4391-93c2-e76471f3d7eb Zigbee Thing
────────────────────────────────────────────────────────────────────────────
? Select a driver. 6
connecting… connected

D:\SMS-107Driver>

Now paste the complete fingerprints.yml file. From the first to the last line.

This is fingerprint.yml contents

fingerprints:

  • id: “MAX Electronics/SMS-107”
    deviceLabel: “SCIONIX SMS-107”
    manufacturer: “MAX Electronics”
    model: “SMS-107”
    deviceProfileName: “multi-sensor-000”

and config.yml

name: ‘Multi-Sensor SMS-107 Driver V016’

packageKey: ‘maxelectronics.scionix.sms107 V016’

description: 'Edge driver for SCIONIX Multi-Sensor SMS-107

vendorSupportInformation: ‘http://www.jjansunyi.co.kr

permissions:

zigbee: {}

First line should be

zigbeeManufacturer:

See here for an example:

1 Like

the meaning is not clear
Do you mean that “fingerprints:” should be replaced as “zigbeeManufacturer:” ?

Great !!!

It works..

Thanks a lot …

1 Like