Skip to content
This repository has been archived by the owner on Jun 25, 2024. It is now read-only.

iotkit-agent resets attributes on enableiot.com #82

Open
ICRI-Cities opened this issue Dec 7, 2015 · 5 comments
Open

iotkit-agent resets attributes on enableiot.com #82

ICRI-Cities opened this issue Dec 7, 2015 · 5 comments

Comments

@ICRI-Cities
Copy link

When setting attributes either via the REST interface or the dashboard for a devices, if the device has the iotkit-agent active, the iotkit-agent will erase all custom attributes from the backend, leaving only the attributes it adds. Please stop the iotkit-agent from wiping out that metadata via a device update.

@adrianweber
Copy link
Contributor

In Device API there is no support for adding custom attribute into already existing ones. Device attributes are threaten as one atomic object. Because of that old attributes will be erased, each time when you made a device update.
The same situation refers to iotkit-agent.
For now we do not plan to implement functionality for adding custom attribute into existing ones.

@ICRI-Cities
Copy link
Author

I am confused why you say you do not plan on adding custom attributes. The dashboard for enableiot.com current has the feature for user to add new, custom attributes to the device. So why are you not supporting what the web interface already lets you do?

@marcinma
Copy link
Contributor

marcinma commented Dec 7, 2015

Dashboard actually doesn't add attributes - it get's attributes and then append new ones and do update. This functionality isn't provided in iotkit-agent now.
Since iotkit-agent is open source you can extend it as fork or propose pull request. For now as enableiot is in beta state and we have other more urgent tasks, we are postponing resolving some less urgent issues. We are aware that many things could be fixed or improved yet please remember that each project has its own priorities and limited resources to resolve those.

@marcinma marcinma closed this as completed Dec 7, 2015
@marcinma marcinma reopened this Dec 7, 2015
@marcinma
Copy link
Contributor

We have fixed this issue in latest commit

@pskindel
Copy link
Contributor

This issue is fixed only for REST protocol.

@marcinma marcinma reopened this Feb 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants