I did what i mentioned earlier in the thread with itemizing/preparing and am going to wait for the migration to happen.
Best case: it replaces my non edge backed device with the correct edge version.
Middle case: Even if it doesn’t do the “correct” edge driver, I should be able to switch drivers to the correct one. All of this without (in theory) needing to exclude/delete all my routines.
Worst case: I’d be excluding/including/resetting everything anyway so might as well give the transition a try.
I have a feeling the transitions will happen in waves. Certain device classes at different times.
This is a Philio (or Zipato - different branding but exact same device) Pan-08 blind controller and its fingerprint is 013C/0001/0015. I should let you know that I’ve also tried to draw the attention of @andresg in a different post about this. Many thanks.
I notice that there is a driver for the “Spring Window Fashion Remote,” but not one for the actual shades. (In the current DTH world, SWF has devices for both the remote and the shades - the remote device doesn’t do anything other than report on the battery.)
I’m assuming this means that the shades are controlled by accessing the remote, rather than a direct command being issued to each shade. If this is how it is going to work going forward, so be it - but it means we will not have control over each individual shade, only the group of shades that are attached to a single remote.
SWF are the same as in Groovy - each shade is an individually controllable device. The remote communicates directly with the shades, and only reports battery to the hub.
so basically they are just breaking everything and I should put my hub in the bin and buy a hubitat then , something I should have done after they puled support for my hub instead of buying the aotec
At this point, over 90% of SmartThings customers don’t have a hub. They have a Samsung smart television or smart appliance and they got the ST app because they needed it to setup that device. And even of those that do have a hub, employees have posted in this forum multiple times that most users have fewer than 15 devices and never use any custom code. (Although even those customers might see something break if they have an older device which isn’t being automatically transitioned.) But the vast majority of ST customers probably won’t perceive any change at all.
But for those of us who actively chose SmartThings as a hub-based home automation platform, who carefully weighed the advantages of one protocol over another for each use case, and who took advantage of the truly tremendous customization options that the platform offered—then, yeah, a lot of things will probably need to be manually handled in this transition. And ST is going from being what was once arguably the most user-friendly platform for power users who weren’t actually programmers to one of the least. With very little official guidance on how to make the changes needed.
It’s painful. And it’s more painful than it had to be for those of us in that small percentage of a small percentage of total users. The ones who will be hit hard.
We can all try to help each other, and there is some amazing work being done by community developers, but each person is going to have to do their own research and then select the path forward that seems best to them.
At this point, over 90% of SmartThings customers don’t have a hub. They have a Samsung smart television or smart appliance and they got the ST app because they needed it to setup that device.
Really? Is this true? Are there stats somewhere, or is that just a gut-feel? I mean, yes, if you buy a modern Samsung thing then you technically can join ST - so you can technically count any Samsung consumer as a ST user. But the question is: do people who buy TVs really join ST and actively use it?
An interesting set of numbers to see would be:
how many registered ST users are there
how many active ST users are there
and then from there take population percentages of which versions of hubs/appliances are being used.
It’s not easy to get those numbers, but that doesn’t make it any less interesting.
It’s true based just on the number of app downloads, which jumped from around 150,000 to now 500 million just in the Google play store after the apps for appliances, televisions, and the smartthings hub were all combined back in 2018. They didn’t add over 100 million hubs in a year.
The stat that the typical smartthings user has 15 or fewer devices and never uses any custom code is straight from smartthings employees, and has been said publicly on multiple occasions.
Ah - ok, thru inference. Got it. That makes sense, thanks.
I am dubious that everyone that bought a dryer downloaded the family hub onto it. Do these things come with Family Hub installed and they auto-update when turned on? That would cause those numbers.
The real key metric, of course, would be active users.
I just noticed recently that at my cottage, my Leviton zwave switches show up as placeholders in the IDE and have a driver entry when you look at the three dots in the device itself. They were only connected to a new Aeotec hub last month. At home, the same model switches connected to a V2 hub for a couple of years, do not have the driver choice in the three dots, and have a type of “Z-Wave Switch Generic“ in the IDE. Could it be the hub, or just the timing of adding the “thing”. Note, both hubs are on the same firmware version, 44.09
SmartThings has been slowly adding production edge drivers over the last few months.
If there is an edge driver with a matching fingerprint on your hub then that is what will be used when you add a new device unless you had a custom groovy DTH on your account with the same fingerprint. For now, custom groovy DTHs take precedence, then custom edge drivers, then production edge drivers, then production groovy DTHs.
Thanks. This is very helpful. I am just now getting acquainted with the edge drivers and the new architecture and my knowledge is rudimentary.
Where do I subscribe to bet edge channel? Is there a link?
Thanks
Imagine spending all this time moving all your devices etc to edge only to see ST still mess this all up and we all still have to basically start from the beginning again.
This is why I don’t want to invest too much time transitioning everything over just yet so I can see exactly what’s going to happen.
I brought this up earlier, but it was buried in a longer statement.
While I think I can live with 50 drivers, 200 devices is not gonna cut it for me. (I spent the weekend chopping myself down to 200 from 262. I’m gonna want to put those 62 back eventually.)
A few folks on here have suggested multiple hubs because apparently that’s a thing now - but I keep hearing various reports about it from different forums. Is it possible to have two hubs under one account, where smartthings can act on devices on both hubs, including automating across the hubs?
I can understand the limits on drivers because of the memory assist if the hubs, but the devices are stored server side and so 200 feels like an arbitrary limit.
Also @nayelyz earlier in this thread you had mentioned that you were going to check with the developers to see if the 200 limit for devices could be raised. Any word?
Yes, But my understanding is that the 200 device limit applies whether you have any hub at all. It’s at the account level. So adding more hubs doesn’t increase the number of devices you could have, as I understand it.
With very little official guidance on how to make the changes needed.
