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).
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?
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.
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.
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.