chris
April 14, 2017, 10:12am
28
Kai:
No, as per Simon’s comment on the issue, this feature is only meant for updates through the bindings themselves (which are done on every startup again), but not for user-driven changes that would be lost after a restart.
I propose to remove this limitation -:
master ← cdjackson:rest_save_thing_config
opened 10:09AM - 14 Apr 17 UTC
This proposed to remove the restriction that thing configuration parameters can … not be updated if the thing is not managed. Note that the limitation still remains for the thing itself.
Justification/use case for this: Even if a thing is not managed - ie it's configured through text files - the user may want to update configuration for the duration of the session. Currently this is impossible - configuration of the thing must be undertaken through the text file, which means the thing is reinitialised (removed, and re-added).
I don't think this has any bad side effects - I guess there's a philosophical question of "is this a good idea" in general, but I believe the use case above is valid and this is currently an issue in OH2.
Signed-off-by: Chris Jackson <chris@cd-jackson.com>
Justification/use case for this: Even if a thing is not managed - ie it’s configured through text files - the user may want to update configuration for the duration of the session. Currently this is impossible - configuration of the thing must be undertaken through the text file, which means the thing is reinitialised (removed, and re-added).
