[ST Edge] Aeotec Recessed Door Sensor Gen 5 Mod ZW089-A

Developer Programs Writing Edge Drivers
1

I added the fingerprint (mfr:0086 prod:0102 model:0059) for this contact sensor to the Stock Z-Wave Edge Driver. I am able to pare the device with this Edge Driver, but it is stock in the open position. The LED in the contact sensor shows the status change when the door is opened and closed but the App does not show the status change. I have also changed the diver to the Stock Z-Wave Edge Driver with no change.

Previously it was using the stock “Z-Wave Door/Window Sensor” DTH and worked fine. Historically the device only reports open/closed and battery.

Any ideas on how to fix this?
@nayelyz

2

Have you checked the Hub’s logs? There you can see if the configuration was completed and how the incoming events are being handled.
You can capture the logs from the moment you pair the device and when the events are not being shown in the app. Then, share that with me over DM or sending an email to build@smartthings.com

3

I have this device, and it stoped working so I hit the forums. Apparently it had been migrated to an edge driver based on the “driver” option on the device. I have even completely removed the device and re-added it. Still will not report any status changes, unless I change the driver to a switch and back to a sensor, then it will update with the current status once and no more.
@nayelyz What was the resolution here?

4

Welcome back to the SmartThings Community, @Controlbreak!

Please, help us by providing more info:

  1. In the “driver” option that appears for the device, does the name Z-Wave sensor appear?
  2. Check the driver’s logs since you pair the device, this provides the info on which driver it is using, the device’s fingerprints, supported clusters, events, etc.
    To do so, you need to:
    a. Set up the CLI (here are the instructions).
    b. Use the command smartthings edge:drivers:logcat --hub-address={IP address}
    Note: You need to replace {IP address} by the actual IP address, which is included in the IDE > “My Hubs”
5

  1. Yes it is listed as the Z-Wave Sensor.

  2. I will work on setting up the CLI over the weekend to pull the logs and report back once I have them.

Thank you for the response.

1 Like
6

Ok, I have installed the CLI and then connected to the hub and driver. Then I opened/closed the sensor, removed the sensor, then added it back, and finally opened/closed the sensor again and here is the log out put:

────────────────────────────────────────────────────────────────────
 #  Driver Id                             Name
────────────────────────────────────────────────────────────────────
 1  f2f2679a-24fb-40da-9322-4c85988e9b53  Z-Wave Garage Door Opener
 2  d58d8432-ea22-4d38-8300-2bd75fdf1358  Z-Wave Sensor
 3  2cbf55e3-dbc2-48a2-8be5-4c3ce756b692  Z-Wave Switch
 4  d620900d-f7bc-4ab5-a171-6dd159872f7d  Zigbee Motion Sensor
 5  f2e891c6-00cc-446c-9192-8ebda63d9898  Zigbee Switch
────────────────────────────────────────────────────────────────────
? Select a driver. 2
connecting... connected
2022-08-01T13:55:38.148579831+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T13:55:38.156041831+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-08-01T13:55:38.168372706+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T13:56:23.798559086+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T13:56:23.808360878+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
2022-08-01T13:56:23.814526169+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T13:56:49.388542256+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T13:56:49.398368172+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-08-01T13:56:49.404627839+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T13:56:54.135695965+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T13:56:54.139783131+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
2022-08-01T13:56:54.146113423+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T13:59:54.778538080+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T13:59:54.788373038+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-08-01T13:59:54.794587288+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T14:00:45.628775753+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:00:45.632555336+00:00 INFO Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received lifecycle event: removed
2022-08-01T14:00:45.638779086+00:00 TRACE Z-Wave Sensor  <ZwaveDevice: 2efe69ba-90b3-46fe-acc8-946da7105918 [16] (Laundry To Garage)> received unhandled lifecycle event: removed
2022-08-01T14:00:45.641974586+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T14:00:45.646333961+00:00 DEBUG Z-Wave Sensor  Laundry To Garage device thread event handled
2022-08-01T14:01:45.799295677+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:01:45.810054052+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ee70e80c-c6e4-48f1-b97e-3fe8e26e67c9 [15] (Back Door)> received lifecycle event: infoChanged
2022-08-01T14:01:45.823801718+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:01:45.827247010+00:00 DEBUG Z-Wave Sensor  Back Door device thread event handled
2022-08-01T14:02:08.028734721+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:02:08.043038763+00:00 TRACE Z-Wave Sensor  Z-Wave Device: ccd6a0d6-b744-48c9-be74-3dd7a97cab70
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
2022-08-01T14:02:08.046298721+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received lifecycle event: added
2022-08-01T14:02:08.055115513+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:02:08.058456096+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received lifecycle event: doConfigure
2022-08-01T14:02:08.065655388+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:02:08.069514513+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> emitting event: {"attribute_id":"tamper","capability_id":"tamperAlert","component_id":"main","state":{"value":"clear"}}
2022-08-01T14:02:08.087761388+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> emitting event: {"attribute_id":"contact","capability_id":"contactSensor","component_id":"main","state":{"value":"closed"}}
2022-08-01T14:02:08.098571513+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:08.105556971+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:02:08.108920054+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:08.116416138+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:02:08.124557346+00:00 TRACE Z-Wave Sensor  Found CapabilityCommandDispatcher handler in zwave_sensor
2022-08-01T14:02:08.130039471+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="BATTERY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-01T14:02:08.138974013+00:00 TRACE Z-Wave Sensor  Z-Wave command(2cfdbd86) queued for radio transmission: CC:Battery, CID:0x02
2022-08-01T14:02:08.142578971+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> sending Z-Wave command: {args={sensor_type="DOOR_WINDOW"}, cmd_class="SENSOR_BINARY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x0A", src_channel=0, version=2}
2022-08-01T14:02:08.148004513+00:00 TRACE Z-Wave Sensor  Z-Wave command(cddb5ffb) queued for radio transmission: CC:Sensor Binary, CID:0x02
2022-08-01T14:02:08.151018763+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:08.159422263+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:08.390679388+00:00 TRACE Z-Wave Sensor  Z-Wave command(2cfdbd86) transmit status: TRANSMIT_COMPLETE_OK
2022-08-01T14:02:08.484085679+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:02:08.492190304+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received lifecycle event: infoChanged
2022-08-01T14:02:08.503630804+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:02:08.506601596+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:08.546878346+00:00 TRACE Z-Wave Sensor  Z-Wave command(cddb5ffb) transmit status: TRANSMIT_COMPLETE_OK
2022-08-01T14:02:08.695496929+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T14:02:08.700405846+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={sensor_value="DETECTED_AN_EVENT"}, cmd_class="SENSOR_BINARY", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-08-01T14:02:08.707395179+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.710776263+00:00 WARN Z-Wave Sensor  Attempted to generate event for ccd6a0d6-b744-48c9-be74-3dd7a97cab70.main but it does not support capability Water Sensor
2022-08-01T14:02:08.713921471+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.717202971+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> emitting event: {"attribute_id":"contact","capability_id":"contactSensor","component_id":"main","state":{"value":"open"}}
2022-08-01T14:02:08.726721013+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.730434846+00:00 WARN Z-Wave Sensor  Attempted to generate event for ccd6a0d6-b744-48c9-be74-3dd7a97cab70.main but it does not support capability Motion Sensor
2022-08-01T14:02:08.733550679+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.736526346+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.739522013+00:00 WARN Z-Wave Sensor  Attempted to generate event for ccd6a0d6-b744-48c9-be74-3dd7a97cab70.main but it does not support capability Temperature Alarm
2022-08-01T14:02:08.742666596+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:08.745922138+00:00 WARN Z-Wave Sensor  Attempted to generate event for ccd6a0d6-b744-48c9-be74-3dd7a97cab70.main but it does not support capability Smoke Detector
2022-08-01T14:02:08.749123638+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:02:09.415275471+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T14:02:09.421251346+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={battery_level=100}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="S0", payload="d", src_channel=0, version=1}
2022-08-01T14:02:09.431660346+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2022-08-01T14:02:09.434986804+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":100}}
2022-08-01T14:02:09.444928513+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:03:09.019220180+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:03:09.028353486+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received lifecycle event: infoChanged
2022-08-01T14:03:09.041171366+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:03:09.044450059+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:03:09.188440944+00:00 TRACE Z-Wave Sensor  Received event with handler device_lifecycle
2022-08-01T14:03:09.201600070+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ee70e80c-c6e4-48f1-b97e-3fe8e26e67c9 [15] (Back Door)> received lifecycle event: infoChanged
2022-08-01T14:03:09.208642547+00:00 TRACE Z-Wave Sensor  Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-08-01T14:03:09.212135632+00:00 DEBUG Z-Wave Sensor  Back Door device thread event handled
2022-08-01T14:05:31.808556613+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T14:05:31.812672696+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
2022-08-01T14:05:31.818839030+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:05:46.398544365+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T14:05:46.408381698+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-08-01T14:05:46.414669823+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
2022-08-01T14:05:51.488546699+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2022-08-01T14:05:51.498359157+00:00 INFO Z-Wave Sensor  <ZwaveDevice: ccd6a0d6-b744-48c9-be74-3dd7a97cab70 [17] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
2022-08-01T14:05:51.504716907+00:00 DEBUG Z-Wave Sensor  Aeotec Open/Closed Sensor device thread event handled
7

So, is this event generated after you already paired the device and open/close the contact sensor?

Checking the handler for the contactSensor capability, we see the event type for BASIC.SET is not included:
image

In this case, only the initial event SENSOR_BINARY.REPORT is detected as an event for this capability.

Could you provide the device model, please? I know it’s an Aeotec sensor but I need the model to check more specifications about it here:
https://products.z-wavealliance.org/products/

8

Ok, I do not know if this has anything to do with it, but this is what I have found. In the fingerprint file here: Z-Wave Sensor
There is no productType: listed for the matching manufacturerID and productId, where most of the other fingerprints all have it.

  - id: 0086/0059
    deviceLabel: Aeotec Open/Closed Sensor
    manufacturerId: 0x0086
    productId: 0x0059
    deviceProfileName: contact-battery-tamperalert
9

Here is the device from the site you listed: Aeotec Recessed Door Sensor

Edit: Answering the original question that I missed. Yes, that was after I paired the device and opened and closed the door a couple of times.

Thank you for the support.

10

Thanks for the info, I forgot the model was included in the topic :face_exhaling:
I’m asking the team to see if they know something about this particular device. If we need more info, we’ll let you know :smiley:

1 Like
11

Following up on this issue, the team mentioned that the event is coming in and their logs are:

//open
{args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
//closed
{args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}

However, those events are not considered in the default handlers, so we’ve created a report to add handlers for that kind of event.
So, for now, you can keep using your device by following these steps:

  1. Delete the Z-Wave sensor driver. You can do that from the app:
    • Open the ST app and delete the device, then, go to your Hub’s details
    • Select “driver”, tap on the driver’s name, and click on “delete” (there must not be installed devices that use this driver for it to be deleted)
  2. Copy the stock DTH (here’s the link)
  3. Go to the IDE and select “My Device Handlers”
  4. Click on “Create new Device Handler”, go to the “From Code” tab and paste the DTH’s code
  5. Change the DTH’s name (this is highly important) and tap on “create”
  6. Once it opens the editor, you’ll see a button with the text “publish”, click on it:
    image
    image1892×138 13.1 KB
  7. Now, try to pair your device again, it should take the DTH as its controller.

Please, let me know your results.

1 Like
12

Thank you for that. I have another door sensor, a newer Aeotec door sensor, that is using the Edge driver and is working as intended. I would have to delete that device as well in order get the driver removed and re-onboard both devices then rebuild the automations running on it. Let me think on this; if I want to rebuild all of this or just wait it out and be surprised one day when I get notifications from the door again.

13

Mmm that’s true, then try to see if the custom DTH still has more priority than drivers.
Just uninstall the device, create the custom DTH and try to pair it again.

1 Like
14

Ok, I followed all the steps above, except the deleting of the driver.

End result was the device still using the Driver and not the DTH.

15

Hey @nayelyz,
I have some great news: I was continuing to work on this topic due to my need to participate in the solution of my problems, and I had some really good luck that I thought I would share. It is more of a work around than a fix, but it might help others with this issue.

Since Aeotec released their official edge driver channel, I started looking into all the documentation on their site. I found this troubleshooting guide for the Gen 5 Recessed sensor. At the bottom of the guide, they reference “Binary and Basic” reporting. This got me thinking about the cmd_class=“Basic” you pointed out in the logs. Here is what I did:

  1. I found the great edge driver created by @Mariano_Colmenarejo here and installed it to my hub.
    a. This driver allows you to make configuration changes to Z-wave devices connected to the hub.
  2. Changed this device’s driver to the “Z-Wave Device Config Mc” Driver
  3. Closed out the SmartThings app (Andriod) for the caching issue.
  4. Ro-opened the app to the device and set the parameters from the troubleshooting guide.
    a. Parameter 121 [4 byte dec] = 272
  5. Hit the wakeup button on the Sensor.
  6. Waited a good 10 min for things to settle in. This may have been overkill.
  7. Changed the driver back to the stock Z-wave Sensor
  8. Closed out the SmartThings App
  9. Opened the app back up.

The device is now showing the correct status and updates/runs routines properly.
I do not know if this will help the everyday consumer for the big edge conversion but might be helpful for some.
Thank you again for all the support with this topic.

2 Likes
16

FWIW, I’ve got a Gen7 Recessed Sensor and I can’t seem to get it to use the Edge drivers. I’ve unpaired and re-paired without success. I’ve verified the thumbprint is in the official edge drivers list - SmartThingsEdgeDrivers/fingerprints.yml at production · SmartThingsCommunity/SmartThingsEdgeDrivers (github.com) but it just doesn’t seem to pick up the edge driver.

Not really sure what to do at this point other than wait until Groovy goes away and see if it converts over without any issues.

17

The # at the beginning of the line means that the fingerprint is currently commented out, and therefore isn’t being used. Your fingerprint is available in the beta driver though, which you can install from the channel linked in the first post of the topic below.

18

The # at the beginning of the line means that the fingerprint is currently commented out, and therefore isn’t being used. Your fingerprint is available in the beta driver though, which you can install from the channel linked in the first post of the topic below.

Ahhh shoot, I missed that it was commented out. Thanks!

1 Like