I am sure i have swapped around Edge drivers in the past without loosing created automations
Recently i was playing with a Greenwave single socket, it joined with
@Mariano_Colmenarejo driver, i added an automation to the device all good
Swapped the driver to a Smartthings beta driver and back to Marianos and the automation vanished ??
Please put my mind at ease, it has not always been like that, im sure it never used to happen
tried closing/reopening the app or checking
Was the automation using a capability not supported by the smartthings driver?
No, doing that had not occured to me as a fix
Not that i recal jimmy, the device is a simple power reporting socket, the automation would have been a simple on off automation
My experience is that now routines are deleted if the capability or attribute used in the routines does not exist in the driver being changed to.
Before, the routine was not deleted, it was marked as an unknown action and it was automatically recovered when returning to the original driver.
Was reported two times.
@andresg for following the topic and the answer, I don’t know if it’s because of the language, but I don’t clearly understand what they mean.
The operation that existed and that is the ideal is:
If you switch to a controller that has different capabilities, Zwave Device Config, to configure some parameter that smartthings has not put in the profile, the actions of the routines are marked as unknown, but will not be deleted. That’s how it worked and it’s necessary.
This is how the routine looked instead of deleted:
This is how it was recovered when returning to the original driver:
Now, first they are marked as unknown and a few moments later they are deleted.
I just checked it again, losing 3 routines, which each had about 6 devices involved, in addition…
Hmm, so i am not going mad Mariano lol