Hi Julian - I wasn't thinking about the deploy problem, that makes sense.
The configuration node that I'm writing is for insteon devices. There are many devices which are battery operated that also have local settings. In the case of a motion sensor, we can adjust the sensitivity as well as the motion timeout and a number of other settings.
I want to be able to show these settings to the user in the configuration node's UI, but in order to display the current values, I have to read them from the device when the device is awake.
I know that the device is awake when the user links it into the eco system for the first time.
I guess what I will do is setup an ajax server that provides all of the device's configuration settings when linking the device in, then dynamically create the configuration node in the editor. These values could then be passed in, and will be stored when the user deploys.
This puts most of the heavy lifting on the front end, which I don't love, but it might be a good compromise.
The only other thing I could do is role my own cache / local database.
Here's a video of the linking and config node creation process as it stands: