I have Schlage BE469 lock on SmartThings stock driver. It’s basic driver, with lock/unlock function only. For user codes you can use Smart Lock Guest Access app.
For more advanced driver with all functions and settings, and new LUM we’ll need to wait for @RBoy to finish transition.
How will those of us who don’t have a hub create virtual switches after the groovy cloud is turned off?
And what will happen to the virtual switches that we have now?
(Created through the IDE.)
Hi, @fido
Are you still having this issue? Are you in the beta group? In case you aren’t, did you enroll to the SmartThings Beta Channel and install the appropriate driver?
Hi, @eric182
Were you able to solve this issue?
Thank you for the reply @andresg
I have mot resolved the issue yet, it is low priority at present and something that will be easily resolved by the closure of Groovy
" Beginning September 30, 2022, at 00:00 (PST) we will start migrating devices and SmartApps from legacy Groovy technology to our new technology we call SmartThings Edge, Schema, and more. We expect the majority of supported devices to be fully migrated by the shutdown date for Groovy integrations on December 31, 2022, at 00:00 (PST) ."
New date Dec 31 not October 15?? I guess the change over is not as seamless as they had hoped, few more challenges.
The communication has been…not clear, to say the least. So it appears the various dates are now:
September 30th - migration of Groovy DTH and SmartApps begins
October 15th - new additions to the Groovy IDE are turned off, but view access still exists
December 31st - Groovy is turned off
Sorry, I know that’s a bit childish. But this is getting silly.
At one time SmartLighting was going away then it isn’t. Sorry to all those folks that started converting their SL stuff to Routines only to blow their Routines limits in the process.
We’ve got folks feverishly converting webCoRE pistons to something else.
We have unanswered questions about virtual devices.
There has been no notification/email to the general ST populous about the impending changes. EDIT: I did finally get an email today at 7:23pm CDT.
I know I’m venting and it achieves little other than getting something off my chest but this is truly ridiculous.
Really … by now a large company like Samsung would have learned that communication is key. I really do thinks the changes to the platform will be beneficial in the long term, but they constantly bumble the roll out of all major changes. Communicate … communicate.
What happened that they went from switching all hubs over to Edge on One day (Sept 30) then they gave them selves, a few weeks (October 15) to now auh … we will need months (December 30). I wonder what part is not working.
At least they had the good sense to slow things down if it was not working according to plan.
Is this real? On New Years Eve?
Maybe they are actually listening to the chaos storm this has unleashed on the forums. . . but you are probably right they are just realizing it won’t be so simple. In the end, this (more notice and more time to prepare) is far more in line with what I wanted and I think we were told would happen.
I have to agree, despite my belly-aching, slowing things down is smart. But it should never have gotten to this point.
I’m almost wondering if they threw out the shutdown notice just in the community initially to gauge response and fish out what they have perhaps not thought about. But we also know that generally the power users are not who they care about. So who knows.
I received an email notification today.
Yes, I just got it myself.
I did, too, except I wish it had listed the specific DTH‘s and smartapps that triggered my getting the email. Obviously they know that information: that’s why they sent it to me.
It’s neither childish nor silly. Samsung has had two years to formulate a solid, well-documented plan, communicate that plan to their end user community and provide regular, substantive updates as to their progress. They’ve done none of that. The entire Groovy EOL demonstrates that we’re dealing with a poorly-run IT shop that is devoid of discipline, rigor and leadership. While it’s been a tremendous amount of work migrating to another solution, I’m glad my relationship with ST is finally coming to a close.
I’m thinking you give them too much credit and this is a boilerplate email to anyone with an account. I received the email too tonight and had completely deleted everything in 2020. Apps, devices, etc. when I finished my transition to another platform and turned off my V1 hub.
Why does Samsung continue to insist upon breaking stuff that works just fine? The is the second time now Samsung team has “transitioned” to a new platform in the name of betterment only to leave behind a bunch of perfectly good working apps and drivers.
It would appear that the expectation for many groovy based smartapps is replacement via lua Hub Devices.
It sure would be nice if the lua API exited beta status before the deprecation announcement. What is the expected duration between general availability of the lua API and the destruction of groovy smartaps? I hope the answer isn’t negative.