Eclipse Community Forums: Eclipse SmartHome » Persistent data for a binding

Home » Archived » Eclipse SmartHome » Persistent data for a binding

Persistent data for a binding [message #1753954]

Mon, 13 February 2017 05:25

Eclipse User

How do I make a persistent data result for a binding? Can I change the configuration of the binding and then save it out to persistent storage? I am using editConfiguration but it seems to not save the data back out to persistent storage. Is there a way to make this happen? Or should I store this in something else?

Thanks,
David.

Re: Persistent data for a binding [message #1754056 is a reply to message #1753954]

Tue, 14 February 2017 03:19

Eclipse User

It depends on what data you want to store. You can access the "userdata" space through ConfigConstants.getUserDataFolder() and create a subdirectory if you need complex data. If it is about changing thing configurations, you can do so within your handler (but note that it will only be persisted, if the Thing is defined in the database and not in a static *.things file).

Re: Persistent data for a binding [message #1754134 is a reply to message #1754056]

Tue, 14 February 2017 11:32

Eclipse User

I want to change the bridge configuration. I do have it defined in a things file though... Tricky Wink

If I do it without it being in a thing file, can I setup the config pieces in code so when you go to add the bridge it will show the config requests? It is an access key I have for an oauth connection. I need to store it somewhere so I can get it back next time. There is no way to persist the config when it is in a thing file? I can see other config options that the user changes are persisted in there, just not the data I am trying to set in the code.

Re: Persistent data for a binding [message #1754197 is a reply to message #1754134]

Wed, 15 February 2017 04:01

Eclipse User

The user has to decide: Either he provides the configuration himself (incl. the OAuth token) in a things file OR he stores the Thing in the database (by creating it e.g. through the Paper UI) and manages it through UI/code.

If you use e.g. a credentials OAuth flow, that might be ok: You have the credentials within the static thing configuration and get a new access token during runtime (which is kept in memory and not persisted, but that's fine).
For other cases, the recommendation to the user should probably be to NOT define the Things statically, but rather use discovery and creation through a UI.

Re: Persistent data for a binding [message #1755399 is a reply to message #1754197]

Thu, 02 March 2017 16:58

Eclipse User

I am making all my stuff through discovery. I don't like config files at all which is why I am writing these bindings in the first place. I hate to write a config file, because it is more maintenance to keep them up to date. This means I was making the thing through the discovery setup but it was still not writing the value out. I ended up using the zwave technique of writing my own separate file, as you pointed out above, but really it would be better if the config saved itself out.

Re: Persistent data for a binding [message #1755416 is a reply to message #1755399]

Fri, 03 March 2017 02:59

Eclipse User

How did you edit the configuration? If you call editConfiguration() and updateConfiguration() from within your ThingHandler, it should definitely be persisted. If this is not the case, please enter an issue about it!

Previous Topic:	Build failed Eclipse SmartHome Model Items
Next Topic:	How to Pre-populate "Location Field" for Thing in Paper UI's autodiscover Inbox

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 16 10:43:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter