I wish they would immediately convert everything they have drivers for, and letâs see what the residual is. I donât understand why they donât convert all the devices they already have drivers for.
With the platform change to edge drivers and more local execution groovy and the IDE are being shutdown in a few weeks so no new DTHs and the info in the IDE will likely be inacurate.
Youll need to look for an edge driver to support your device.
What is the device and someone might be able to help you find one.
You need to subscribe to the authorâs channel and then select the driver you want to be installed to your hub. For the stock Smartthings drivers, you subscribe here:
fwiw, i have that same plug which had been migrated to a stock driver. i just changed it to Marianoâs driver which has a lot more options and settings
I worked in IT for years. Every company I worked for implemented change moratoriums during periods that were deemed critical to the business or for when they expected extremely heavy activity. Samsung is making what is probably the largest change ever made to the SmartThings platform just as new hubs, sensors, thermostats, etc. are being unwrapped and new users are coming onboard.
Has anyone else has issues with Zigbee devices going offline? I only have two (most devices I have are Z-Wave) but ever since migrating to Edge drivers my motion sensor and doorbell relay have worked fine for a few days and then gone offline.
This could be unrelated to the drivers and be down to the hub firmware upgrade that happened at a similar time. I removed and re-added the motion sensor as thatâs easily accessible and that fixed it for a few days but it seems once they go offline they donât come back online.
I havenât seen anything that Iâd consider a real fix. Youâll find a few things that seem to work for some people some of the time.
Assuming youâve got an Aeotec or V3/2018 hub, the trouble seems to have started with firmware 45.9. The release notes mention a replacement of the ZigBee stack for those hubs.