Hi @andresg - not sure which part you are referring to as I had two problems with this Dimmer.
The flicker problem: this was solved by changing a parameter in the Settings of the device. That was a bit of a surprise for me - the Edge Driver actually changed parameter settings for me, and that meant that my lights, not being compatible with that setting, started flickering so badly that it made that room unusable. I advised Aeotec about this and they were supposed to make a change so that parameter settings do not change simply because an Edge Driver is assigned to a device.
The disconnection problem: This happened only once to me. Presumably, I was doing so much testing at the time and excluding and including so many repeater devices, that it must have affected the mesh badly. I did a few Zwave repairs after I re-included the Aeotec Dimmer and since then it seems fine.
Sorry if these specific questions were covered but I couldnât find it.
I have I use Rboys LUM as I have 6 Schlage locks on my house. Will I have to move them to an Edge driver before Sep 30th or will they be moved automatically? If they are not moved I really donât want to have to have rejoin them to the Hub.
A second question, any suggestion on Edge Driver I should use?
If I may, I would like to point out this other post of mine, to which no one from ST replied⌠This is about a device of which have 12 in operation at my home. These are Philio Pan08 Blind Controllers (sometimes branded Zipato Micro Module Motor Controller Pan-08). This is the fingerprint from my earlier post.
These devices always included without any need of a Custom DTH. ST always included them automatically using the stock DTH Zwave Window Treatment. I literally needed to do no manual change.
Now these devices will not include as anything other than Zwave Switch, which means their fingerprint is not included in the new ZWave Window Treatment Edge Driver. Which means, likely, that come 1st October I will lose these devices and they will either be added as a Zwave Switch with On (open) and Off (closed) - or as a Thing.
Can you please check whether this is indeed the case?
Iâm curious exactly how you did that, did you unpair and then repair the device (letting ST pick the handler), or install a stock DTH via IDE. If the latter, did you do anything to ensure a matching fingerprint?
In my case Iâve also eliminated all but a couple of custom DTHâs, but suspect I may still have âfully functional but incorrect stock DTHsâ assigned in some cases.
Same here, including removing a couple of rboyâs stuff. I can always add his stuff back if needed. I will also wait for the ânewâ Smart Lighting before moving some of my automations back.
Most of my devices were installed before I added any custom DTHs to my account so Iâm pretty sure theyâre correct.
At some point I installed a couple of custom DTHs for Zooz Zen26 and Zen27 devices. I changed some devices to use those via the IDE. I disliked the lag induced by cloud execution so I changed them back.
Once those DTHs were installed they were, of course, selected automatically when I paired a new device. In all cases after reviewing the device parameters via the IDE, I changed to the appropriate stock DTH.
All this is probably a year ago. I havenât added a new device or reset/reconnected an existing device in ⌠several months.
Iâm not cutting edge here and Iâm confident my simple devices are using the correct DTH.
@mcvoss Rboyâs LUM is a smartapp, not a DTH. Since it is based on Groovy, it wonât work after the transition. I believe Rboy is working on transitioning, but I have no idea if it will happen.
Sorry, let me rephrase. I use LUM with Rboyâs DTH. I know they will both not exist, at the moment past 9/30.
While using his DTH does anyone have any idea if Smarthings will find the correct Edge driver. Does anyone know the correct EDGE driver to install on my HUB at the moment for the transition?
I get what you are saying. You can switch your DTH back to a ST stock lock DTH (I use LUM with the stock DTH now) if you want. ST should automatically migrate to Edge when the transition comes.
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.
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?
" 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.
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.
