Skip to content
This repository has been archived by the owner on Jul 28, 2021. It is now read-only.

AppClient adds additional attributes to payload on CommandPublish #50

Closed
tomanwalker opened this issue Aug 18, 2016 · 2 comments
Closed

Comments

@tomanwalker
Copy link

Example:
Intended payload
{"myNumber":201601,"Message":"Test","Interval":30}

Payload received by device:
{"d":{"myNumber":201601,"Message":"Test","Interval":30},"ts":"2016-08-18T10:15:40.108+0000"}

This is very inconvenient due to following reasons:

  1. Requirement for having Parent D attribute has been deprecated by IoTF a long time ago
  2. NodeJS library we use for other application but for communication with the same device Passes the payload AS-IS with No modification

Please, consider changing the CommandPublish function so that it would Not Modify InputData.

sathipal added a commit to sathipal/iot-java that referenced this issue Sep 6, 2016
1.Support for custom message formats like, byte array(binary), String and
JSON
2. Fix for issue ibm-watson-iot#50 - removed the addition of "d" from the payload. Now
the library formwards the message as is instead of additing "d".
3. Fix for issue ibm-watson-iot#45 - deletes the added device types and devices
4. Added tests for the custom message formats
@sathipal
Copy link
Contributor

sathipal commented Sep 6, 2016

The pull request #58 contains fix for this issue.

Lokesh-K-Haralakatta pushed a commit that referenced this issue Sep 6, 2016
Custom message support, fix for #50, #45 and removed historian APIs
@sathipal
Copy link
Contributor

Closing as the pull request #58 contains the fix for this issue.

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

2 participants