I agree but the documentation doesn’t which is confusing, this page http://docs.smartthings.com/en/latest/device-type-developers-guide/device-preferences.html
Says to look at “HomeSeer Multisensor” device code for good example.
Taken from “HomeSeer Multisensor” device code
input "intervalMins", "number", title: "Multisensor report (minutes)", description: "Minutes between temperature/illuminance readings", defaultValue: 20, required: false, displayDuringSetup: true
Includes both title and description.
I have come to many of the same “Guessed conclusions” as you but this is sad that we are all hacking away trying things because the documentation is so bad.
It can’t be good for the servers either. I am always crashing my app, throwing exceptions etc as I hack. I am also doing rapid edit, save, publish, test, edit, save, publish, test sequences because I have to use trial and error (mostly error) to figure out what should have been very easy to document.
BTW: Sample code is NOT documentation. I have seen so many documentation pages that say "Here is a sample of how to use this method for documentation"
With not explanation. That the first save is the button label, the second save is the method to call, the third save is the description of the button. So we have to try changing the values and seeing what the effects are.