How to read parameters initially

[doncaruana]

Well, a lot of spelunking and I think I’ve come up with the answer, based on this thread:

Seeking clarification on preferences{} and actual device params

Hi. Please confirm if my understanding of this is correct: Using preferences{} seems like the proper way to alter device configuration parameters. I’d like to clarify – preferences{} values are stored and populated independently of what the actual parameters are on the device. Let’s say, a user sets param 6 to [0] using preferences{} in the UI. Subsequently, param 6 is set to [1] without user intervention by either the DH or a smartapp. When the user goes into preferences{}, he will see [0] as the current value, even though the device now has [1] in param 6. Is this correct? Could you point me to an example (if you’re aware of one) where configure() (I assume that’s the way it would be done, if there’s a different way, would very much appreciate the info) is used to retrieve current para…

It’s a pity you can’t even show them.

I guess, as a work around, you could set the default value in each preferences and then have them all load at setup with instructions to just hit done and not enter anything. Because once they are set that way, they stay there (what keeps record of them, the hub?).

But…I thought “displayDuringSetup: true” would pop up the preferences page automatically. Doesn’t seem to happen. Am I misunderstanding?