Thank you for your speedy reply!

I'll look into the feasibility of a rollback, although in general that isn't ideal as we would then lose the benefit of any other changes in the latest release.

I don't necessarily need a GUI option for this (though that would of course be best).  I'm happy with a CLI command to do it, because this issue is specific to the CLI anyway.  But so far even the documented commands don't seem to be having any effect.  Have those commands in themselves been disabled (which would be a very serious issue)?

The wider issue of having to use a clunky GUI to issue CLI commands doesn't help of course.  That model has proven unreliable at the best of times, and in particular doesn't seem to give any feedback to indicate whether the command has succeeded, or even if it has actually been run at all.  Please can consideration be given to not disabling the CLI on adopted devices?  Anybody using the CLI can be assumed to know what they're doing, and so simply giving a warning that any local changes might be overridden by the controller would be sufficient.  Then, it would be possible for administrators to test commands locally before configuring them in the controller GUI to be persistent.