Good day, I deleted an Edge driver using the Samsung Advanced Web App and I now when try to reinstall that driver through the web, I get the error-request-failed-with-status-code-500. I have no problem installing other drivers from the same channel. Just this specific one. I tried to install it using the CLI and I get the same error. Any help would be appreciated. Thanks
another user reported the same issue this week - removed driver and can’t install it again:
which Edge driver?
tagging @Itati
Zigbee Moisture Sensor Mc from Mariano Shared Beta Driver
Hey there, bug buddy - i have the same problem, different driver…
And this happened after you deleted the driver from the Advanced Wep App instead of uninstalling it from the channel?
No i deleted mine from the channel
Hi, @Grosbiz
When you deleted it, had you already deleted all the devices?
Could you provide support access to your account, please?
- Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com )
- Log in to your Samsung Account
- Select Menu (â‹®) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
Hi @fredd0
How did you remove it from the channel? When you deleted it, had you already deleted all the devices?
Good day,
When I deleted it, I no longer had any devices using it as I made sure to delete the device before deleting the driver.
I have provided support access to my account.
Thank you
Now that you mention it… i don’t think i did.
I might have though. I also provided access to my hub
@Itati good day, any update?
I feel abandoned…
The issue has already been reported. Currently, the team is working on a problem related to the LAN driver. The solution may take some time. We will notify you as soon as we have more information.
Thanks!
Thanks for the update. This driver is a key integration in my routines. I’ll be waiting eagerly
I think I’m going to buy a new hub for the time being and return it if this gets fixed in the reform window…
hopefully the migration doesn’t bring whatever is corrupted in my hub with it
The new update didn’t fix my problem… so sad
Not sure if it was supposed to…