I everyone. I tried to replicate the first issue of changing a preference’s data type which made the “Settings” option disappear, but I was unsuccessful. In case it happens again, please report it before changing anything so we can investigate it further.
Can you elaborate on what “it will break” means?
We got another report about the driver not “syncing” with the latest version of a custom capability (new attribute/commands, etc. meaning we get an error in the logs when trying to use the new config in our driver) and, here I shared the feedback from the engineering team to clarify some things about this behavior: