Time is getting tight for auto migration.
I have two sets of kitchen lights one on a Zemismart 2 gang switch and the other on a candeo dimmer.
Neither have migrated to edge.
And both have quite a few automation routines so Iâd rather not delete and re-pair to force the issue.
It so happens I have an unused Zemismart 3 gang switch which I paired today to see if it picked up a stock edge driver,
It paired as a stock edge zigbee switch but that only exposed 1 of the switches so thatâs pretty uselessâŚ
Iâll be a bit annoyed if the 2 gang Zemismart migrated to zigbee switch at a very inconvenient time like Christmas Eve and stops working
What I did was create a VR switch specifically for this. Go into said device routines add VR switch and duplicate the physical switch State in the if and/or then parts. Remove physical switch from ST, the VR switch preserves the routine. Add the switch back to ST go into the routines of the VR devices and re-add the physical device. Itâs not perfect but it got all my stuff switched over to edge. I wasnât going to wait and pray nothing got broken
The Zemismart 3 gang switches work well with @Mariano_Colmenarejo âZigBee Multi Switch and Child Mcâ. I am assuming the 2 gang will also work with it.
The only thing I can say is to those that are waiting on the migration please do not think itâs going to be a magical everythingâs going to work. Weâve had a huge amount of notice to get things switched over. You could have taken the time and slowly migrated things over manually. I know this is not the ideal way to do things but it definitely prevents things from being broken. With all that being said please do not come on the thread and start whining about how stuff is broken you had plenty of notice to get things switched.
Just about everything that has automatically migrated for me, has been smooth. The handful of devices Iâve moved manually have taken significant work to correct automations, and most of those were less tied up in routines than the ones that are still pending. I know 12/31 was the original timeline but given how long ST is taking to move even simple devices like GE/Jasco switches, I have no expectation that the plug will be pulled on the Groovy server 12/31 11:59pm. Theyâll get moved eventually and itâs easier to wait than to do it myself. In the worst case, they stop working and I have to reconnect them the same way I would now, but in the meantime Iâd rather spend those hours fixing the complicated SmartApp / DTH integrations that are truly going to break, like MyQ and webcore pistons.
I had about the same issue back in September, some devices (but not all) stopped responding, and I wasnât able to re-add anything, nothing was being discovered. Funny thing, even the factory reset of the v3 hub didnât help, because it was pulling all the drivers back upon the setup. The only thing helped was the manual driver clean up: I had to remove all of them and carefully added one by one before discovering the devices. I guess at certain level too many drivers prevent the hub from operating properly.
Same thing for me with keen vents not having edge drivers. I opened a help ticket months ago and told just wait for the finial migration. That is what less than 3 weeks away and just tested last night my keen vents do not connect with edge drivers.
I disagree 100% on this. Moving almost 100 devices, with all the automation takes a lot of time, especially since they also have to be re-created in ActionTiles. SmartThings said the migration would start October 15 and end Dec 31st. For me they have migrated a total of 9 devices. I have migrated a few myself. I donât have the time to migrate everything. So if things are broken over the next two weeks, yes I will come on this thread and complain. Loudly. So you better block this thread.
You have every right to feel frustrated. I too wish that more of my devices would have been migrated by now (only 5 for me).
At the same time complaining loudly on a forum is just preaching to the choir and making us all suffer. Weâre all in the same boat here.
Calling/emailing support would be a better use of the loudness. Post on twitter, tagging Samsung. Something other than loudly complaining to the other folks who are dealing with the same issues as you.
I migrated over 200 devices. I took the time to convert all my automations I from webcore and updated all my rules in sharptools. It wasnât hard, I didnât it room by room. So I donât want to hear about how hard it would be or how long it would take.
@Shanapadila This might be device that only @Mariano_Colmenarejo can help with.
Mariano this smart vents are zigbee devices with temperature sensor and open/closed/level capabilities.
Perfect for your virtual thermostats approach.
Each vent could have itâs own control
However, I find your view quite hard line and condescending, although I am sure some would agree with you hence the use of the I, whilst other may agree with me or have a totally different opinion. I do think this potentially may be off putting for any users new to the forum who want to reach out and find solutions in a post Groovy world, which I imagine there may be many after the 31st December.
Everyone has different needs and demands on their personal time. Automationâs have been set up to make life easier, some over a long period (years in most cases), doing a big bang migration was probably not in anyoneâs plans when they setup their kit, based on another entities schedule (Samsung).
I could agree on your rather hard stance about manually migrating if drivers had been made available more stably before the planned migration date, and there was no promise of automatic migration from Samsung, but in both cases this was not true.
As per a previous poster, I invested my limited free time in figuring out the things that would break post Groovy, and implemented solutions for them, so like a great many people we have not been sat around expecting it all to go swimmingly. However when the vendor is alluding that there are devices that will migrate, you have to believe that there will be at least an element of success in that process, albeit there will be outliers that need fixing.
The community is here to help others, and knowing the status and approach of other peoples migrations is all valid input for them to make a choice on how they personally wish to handle the migration.
Lets welcome everyoneâs input on the forum, and ignore/skip items that are of no personal interest, that way we are all empowered.
Dear Santa! Please, please, please make this Edge migration as frustration-free as possible. And please do not throw another huge system change upon us for a while - say several years. Many of us would like - for a change - to enjoy the Smart Home they invested. Thanks!
To be clear, when you say you migrated over 200 devices.
Did you delete the devices and lose all the automations then pair the device again using a community or stock edge driver?
This might be all fine for you if you are content to do that, for me I have lots of dependencies and virtual switches which drive logic, it would be a complete pain to have to re-implement that , especially in bulk, on a mobile phone app.
As far as I understand there is no means to swap a device from a DTH to an edge driver âin situâ - this is what migration does. If there was a means to do an in-situ swap to edge Iâd be happy to go that route.
Dear Santa! Please, please, please make this Edge migration as frustration-free as possible. And please do not throw another huge system change upon us for a while - say several years. Many of us would like - for a change - to enjoy the Smart Home they invested. Thanks!