The End of Groovy Has Arrived

Anyone know if this candeo zigbee dimmer is handled by the stock edge driver?

  • application: 01
  • endpointId: 01
  • firmwareFullVersion: 01006750
  • firmwareImageType: 60
  • firmwareManufacturerCode: 4107
  • manufacturer: Candeo
  • model: HK-DIM-A
  • zigbeeNodeType: ROUTER

I looked in the switch and dimmer-remote fingerprints and didn’t see them.


Woo Hoo, 14 Ikea warm white GU10 bulbs have migrated for me.
Just 4 Ikea White colour temperature bulbs to go.
(Well one Secure/Horstmann SSR303 boiler actuator too, but that is directly controlled by it’s wireless thermostat; so not especially worried about it).

1 Like

I had both my 2 Smartthings Motion Sensors IM6001-MTP migrate to edge today. I changed driver for one of them to Mariano’s ‘Zigbee Motion Sensor Mc’, works well so far.

Thanks, does anyone know what happens if the fingerprints are not present in the stock SmartThings driver but are present in. Community edge driver (already installed on the hub) will the migration process just ignore the device or would it automigrate to the community driver?

Community Edge drivers that are installed on the hub and that have fingerprints that match the device are preferred over stock drivers.


The order is given in the official transition FAQ. Custom drivers are top priority if there is an exact match on the fingerprint.

1 Like

7 posts were split to a new topic: Pair devices to a driver

Ive had one of two Smartthings motion sensors migrate - I had assumed they were identical units so is it normal for one to be on edge while the other is unchanged? The first time I looked at the migrated device in the app the Battery level just showed as a dash - but this seemed to fix itself a short time after.

Isn’t this page Migration List supposed to be updated every week, with recently added drivers highlighted in bold?


For those still having problems with the Wi-Fi mesh hub models and edge drivers, there’s a new update that is supposed to help with some edge, driver issues, but not all. Note that you must have updated the Wi-Fi router side to the most current version or the home automation side won’t update.


The way I read that wasn’t as a week-by-week migration but instead a list of all the devices that we know have a new Edge driver available when the migration does (eventually) happen.

But, the point I was making, is that the list is not being updated as promised (with bold text week on week) to show which devices now have access to Edge drivers


11 posts were split to a new topic: ST Multisensor Transition Issues with Tilt Detection

My one ST multipurpose sensor migrated today too at 10:45 AM EDT. Checking it later, the battery and 3 axis attributes didn’t have data, took a few swipe refreshes to get it to populate.

FIrst auto migration for me since November.

1 Like

With ST Multipurpose the same thing happened as with ST Motion Sensor - one device migrated but the other hasn’t. Surely this isn’t intended behaviour.

I’m not at all surprised. I have two of the same model dimmers that are side-by-side in the same 2-gang box. One migrated in November, the other still has not.

Ok so then the migration process looks broken - so is the wrok-around to remove and re-install any devices that the hub now has an Edge driver but havent migrated?

There’s no reason to believe that. We’ve never been told how the migration selects accounts and devices to migrate.

If you’re impatient, then yes, you have to delete your devices from SmartThings, remove and custom DTHs, lose your routines. Then recreate everything.

But why? If everything you have is working, just sit tight. Who really cares what driver a device is using it it works?


No one from staff has confirmed, but one possibility is if the devices are used in different types of routines. Remember that migration can affect routines as well. In some cases routines will be deleted if the device had previously been using custom capabilities, which are not supported in the edge driver that the auto migration wants to use. So I think it’s possible that migration might be delayed for one device if its routines are complicated, but not for another of the same model that was only using simple routines.

It’s also possible that although the the two devices have the same model number, they have different firmware, and therefore different fingerprints.

Neither of these situations would mean that migration was “broken.“ It would mean that it was dealing with edge case situations correctly. :thinking: