Yeah I wouldn’t mind changing things just now knowing that if I do, they don’t get screwed again come Sep 30th. Some more info would be good to be fair.
This looks to be a custom edge driver. Will the standard edge driver feature this device too?
Also, for multi switch devices will they appear as a single device? And thus only the master device controllable from Alexa?
This is a huge concern for us “Please note that some devices may not transition automatically and will need to be re-onboarded.”
We have custom DTH for smart locks (Yale, Kwikset, Schlage Zwave) and several different contact sensors ( Zwave and Zigbee) and leak sensors (Zwave and Zigbee).
How can we find out which devices need reonboarding, and which don’t? This is such a massive effort that we if we have to reonboard we will just rather switch
Thanks for getting back to me
The DTH are ones that other people have made available from GitHub and I have copied the raw code to make DTH’s. The smartapps are a combination of smartthings ones and others from GitHub. I am comfortable doing that again, however there is no real information on how to access and install the platform we need to install the new drivers on. I was hoping that Samsung would provide some kind of how to guide rather than just getting the community sort it out for them. What alternative options are there going to be for webcore? Will the new platofrm be capable of more complex automations?
I don’t know that these are the best ones, but I got the Zooz ZST10 700 series zwave stick and the Sonoff zigbee USB dongle plus. There are articles spread around in various locations of the Home Assistant documentation and community with lists of recommendations.
@philh30 has added all the zwave fingerprints from all the currently available edge drivers in the Beta channel to the community-created Wiki Table of Edge Drivers.
So if your zwave device currently uses one of the stock groovy DTHs and it has an entry in this table in the “stock ED “ column, it should be automatically converted when the transition occurs. Hopefully.
You can sort this table by any column, so, for example, to see the list of all the fingerprints in a particular driver sort by edge driver name.
We can still use lots more help if anyone wants to enter some of the fingerprints from the community created drivers to help people find those. Even if you just add one or two it will help. Since people can sort the table however they want, you don’t have to put it in any particular order, just leave the sample row at the top.
Here’s the direct link to the wiki:
And here’s the community discussion thread if you have any questions about the table or the wiki.
Just the z-wave ones so far!
Man I hope you wrote some kind of script to pull all those out Good work!
Sorry for the delay, @MarkTr
I already asked the team about this, so, once I get their feedback, I’ll let you know.
So I decided to make some time for this one today. Exclusion and re-inclusion did not help. At certain percentage settings. the lights kept going up and down constantly, not just during dimming up/down activity, but long after the switch was left alone. I also tried a factory reset but not sure that one worked - even excluded from the network the lights kept going up and down and effectively rendered that room unusable after dark as it drives you crazy. This happened overnight, immediately upon installation of the Edge driver.
Since I had no other identical dimmer switch to compare settings to, I delved into the settings myself, and from there I:
Enabled Overload Protection
Enabled Overheat Protection
Raised the Minimum dimming from 0 to 10
I changed the Dimming Principle from Leading Edge Mode to Trailing Edge Mode.
To my mind, it seems like the last setting is the one that corrected the problem. Either the Aeotec Nano Dimmer does not handle Leading Edge Mode very well, or else my lights were not too happy with it.
In any case, that must be a parameter change that happened upon installation of the Edge driver.
And that means - I’d hate to think what is going to happen to all the parameters I set up on the many devices over the past several months… I have blinds set to report status every so often, more importantly, I have Qubino Flush Relays set to go off so many seconds after going on (very useful whenever Smartthings fails to turn them off, e.g. irrigation…). Pity that during the migration this will happen and we will be none the wiser until we start experiencing problems like these.
If you are using someone’s custom Edge driver and they become disgruntled and decide to delete their channel/driver what what happens to everyone’s hub that is registered to that channel?
This thought had not occured to me, however it is a very good question.
As long as you don’t remove the driver from your hub it will continue to work.
The problem would be if I, as the owner of the channel, published an update that made the driver unusable. That would be a problem due to automatic updates.
The user should be able to disable automatic driver updates.
I was afraid to ask this question, maybe because I already knew thew answer. I honestly assumed that the worst case would be a paid subscription for access, which would be fair in my opinion.
This would offer peace of mind.
Average End User here.
I have zero idea what’s going on here; and even less understanding if this is even my problem to begin with. This post alludes that I should be angry Homebridge is going to quit working?
What do I do; I legit don’t understand. How is this going to be communicated to mass of dummies like me?
From what I gather, the full library of production Edge drivers, migrations and apps aren’t available to the general everyday user until the old environment is also disabled on Sept 30? Why the same day? Why can’t the new drivers and tools be completed first (to a reasonable extent) while the normal users are given the opportunity to test their migrations. It’s like asking a programmer to write code without a set of tools to test against. For a person who depends on their home automation, it’s distressing and infuriating.
They changed the dates. October 15th is when they start shutting down certain parts of the old architecture. The first post in this thread has more details.
Thats just weird… for no real reason i wanted to re read the original post and noticed the same thing …
I also want to know how migration works and why ST have not provided a tool for users to move devices to edge themselves, currently if a user wants to migrate devices they loose automations
Alexa on the other hand does not loose the automation if a device becomes disconnected, it simply disables the automation and indicates a trigger device needs connecting… very elegant
That’s good news, but it also means that as a user, unless the code itself has been shared, you have no way of having it tweaked or improved (say if a bug is discovered down the line). It also means that if you have to reset the hub ever for any reason (not that this has ever happened to me in the last 18 months or so), you would essentially have lost those drivers. Or at least this is my understanding.