Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mapping of multiple aspects #117

Open
sergeyk183 opened this issue Feb 25, 2021 · 2 comments
Open

Mapping of multiple aspects #117

sergeyk183 opened this issue Feb 25, 2021 · 2 comments
Assignees
@sn0wcat
Labels
more info Additional information is required

Comments

@sergeyk183
Copy link

Describe the bug
If my target asset contain multiple aspects (of different type), only one of them receive correct mappings in the Agent after Configuration is complete.

image
@sn0wcat
Copy link
Member

sn0wcat commented Feb 25, 2021

is this start for free tenant or developer tenant? were there any errors in node-red as you were mapping the data?

(Btw, you can always fall back to mapping in the mindsphere UI if you need a quick workaround.)

@sn0wcat sn0wcat self-assigned this Feb 25, 2021
@sn0wcat sn0wcat added the more info Additional information is required label Mar 18, 2021
@sn0wcat
Copy link
Member

sn0wcat commented Mar 18, 2021

@sergeyk183 this seems to be connected to the #116 issue. Do you have a unit configured in your aspect definition. If not could you use something like "-" or "empty" and try again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sn0wcat sn0wcat

Labels
more info Additional information is required
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sn0wcat @sergeyk183