Yep. I’m betting they’ll announce another extension to the planned end of first party driver migrations. Churn in the beta firmware releases makes me think most of their attention is there rather than on driver migration.
I’ve got a dozen devices not yet migrated. Almost all of them are additional instances of make/models I have which were migrated before Christmas.
Me too, one of my first back in November I believe. Still has the old Rboy driver issue of every once in awhile it shows opening and is stuck like that until I open and close it.
They are smart plug
1 from aeotec smart switch 6
1 is a generic brand
aotec was migrated to aoetec smart switch 6 (advanced options)
the other was migrated to z-wave switch
also tried to z-wave switch mc from mariano
nothing in the event, when I click to turn it on/off, it seem to do nothing and kind of timeout after I while
I used a driver named virtual momentary switch to test, it seem to turn on the device and turn it off after a couple of second. This driver is working for them, but it’s not what I want
Any reason for this advice? “By brand” seems superior to “Scan for nearby devices” for zwave/zigbee. It lets you turn on discovery for just one radio without also triggering the discovery function of any LAN drivers.
4 days to go and about 35 devices left. Wonder if they will stick with the revised, revised, revised date and just pull the plug on the 31st. April fool’s!
It might be a revised, revised, revised date but it was still announced on 21st September last year, in the broadest of terms (Q1 of 2023), ten days before the nominal start date of the whole process. As the device I am waiting for hasn’t been ported yet they certainly won’t literally make the deadline but I don’t think they will be all that far off the spirit of it.
I’m at 97 devices left. One light transitioned over as a switch in the last month or so using an existing Edge driver. But as others pointed out, functioning vs the timeline is most important.
So, half of my remaining list will get taken care of when the Hues and Sonos are moved over.
I actually use the community Hue Edge driver for all Hue Rooms, Zones and devices except lights (and boy it is good). I have a feeling whatever ST come up with in their Hue support will be inferior so we’ll see where I go there. But, the number of automations I have with Hue devices is deterring me from regenerating new light devices in the community driver.
My four Harmony devices in the list are Harmony hub devices from the old Harmony integration. I can delete those having moved fully to the community Harmony Edge driver (another well executed and feature-rich driver).
(Yes, I know I need to find a replacement for the Life360 stuff …)
I guess this isn’t surprising. Sort of funny that there is a start date, but no end date… I’ll be curious to see how fast this new process happens, given that most of my devices have yet to transition.
ST has a dedicated Edge driver for Hue in the beta channel. But TBH it looks about the same functionality as Matter would provide…if SmartThings actually supported Matter bridges.