eclipse/ditto

Eclipse Ditto - Digital Twins for Eclipse IoT

Julian

@JulianFeinauer

No clue :o

sry : (

Bob Claerhout

@BobClaerhout

I answered on stackoverflow. Are you wrapping the json in between curly brackets?

ottlukas

@ottlukas

yes the json has wrapping curly brackets

Julian

@JulianFeinauer

Can someone help me with the authorizationContext thing? I’m so confused by the syntax and meaning…

Julian

@JulianFeinauer

I tried to set up a mqtt connection and have no idea why it suddenly works with nginx:ditto :o

Thomas Jaeckle

@thjaeckle

the authorizationContext is simply a list of already authenticated "subjects" (e.g. user IDs)
when creating a connection these "subjects" can be freely chosen and added to the connection (as adding a connection is done as "devops" command with admin-credentials it is kind of a "sudo" situation where each user id can be configured)
normally, something like an OAuth server or a nginx authenticates the user and injects the authorizationContext as list of subjects into Ditto

Julian

@JulianFeinauer

So nginx:ditto means it's the user that would normally be authed via basic Auth against nginx?

Thomas Jaeckle

@thjaeckle

exactly .. at least in the default and sandbox deployment where user "ditto" is already included in the nginx htpasswd

Julian

@JulianFeinauer

Yes

That makes it clearer for me

And what about ditto:inbound-auth-subject?

Thomas Jaeckle

@thjaeckle

that's just an arbitrary subject which must be included in the policy/policies your thing/things are referencing

Julian

@JulianFeinauer

Aaaaaaah

It sounds like a special directive

Thomas Jaeckle

@thjaeckle

ah, I see :D

no magic here, nope :D

Julian

@JulianFeinauer

Would you mind me doing a small pr where I try to make the documentation a bit more... Explizit?

Thomas Jaeckle

@thjaeckle

would be awesome :+1:
do you already have an Eclipse account and did sign an Eclipse Contributer Agreement?
that - and signing your commit - is required so that we are able to accept a PR
see also: https://github.com/eclipse/ditto/blob/master/CONTRIBUTING.md

Julian

@JulianFeinauer

Account I have (lurking on multiple lists) but no ICLA yet, I will sign one...

Julian

@JulianFeinauer

Here you go @thjaeckle eclipse/ditto#594

ottlukas

@ottlukas

My features for my own Thing are shown empty:

{
    {
        "thingId": "tt:mm",
        "acl" : {
            "ditto": {
                "READ": true,
                "WRITE": true,
                "ADMINISTRATE": true
            }
        },
        "attributes": {
            "manufacturer": "TT",
            "ID": 123456
        },
        "features": {
            "properties": {}
        }
    }
}

In properties there I have a list of telemetry data: e.g. "temperature": 20.8,
"humidity": 73, ...and so on. Anyone got an idea what i need to improve?

Julian

@JulianFeinauer

@ottlukas how do you set / update / retrieve the thing?

I had similar issues at first, when I used the API wrong :D

How do you set / update / retrieve your thing @ottlukas

wtf.. gitter :o

ottlukas

@ottlukas

I just followed the Digital Twin example @JulianFeinauer ;)

Julian

@JulianFeinauer

which one? there are tons of… and also I see you use the API V1, is this an older example?

ottlukas

@ottlukas

I am using Postman including the Ditto Json Project

Julian

@JulianFeinauer

Ah, okay, i didnt try that… i stayed with curl for the full fuck-up feeling :D

ottlukas

@ottlukas

I basically using Postman

and yes Postman Ditto seems to use API/1

Julian

@JulianFeinauer

me usually too

can you send a link tot he tutorial?

ottlukas

@ottlukas

https://www.eclipse.org/ditto/intro-hello-world.html

Julian

@JulianFeinauer

and you just created it?

or how far did you go?

ottlukas

@ottlukas

yes the hello world works fine

then i am changing it to my json

and I can greate the thing , except for the empty telemetry data

Julian

@JulianFeinauer

whats the exact json you use for creating

Florian Fendt

@ffendt

@ottlukas In the json of your thing above, you're missing the featureId which should be below features and above properties, so it should probably be something like "features": { "myFeature" : { "properties" : { "temperature": 20.8, "humidity": 73,... } } }

Julian

@JulianFeinauer

@ffendt @ottlukas yes, thats what I also thought, thus I wanted to see the original „create“ json

ottlukas

@ottlukas

{
"definition": "MM:MMExample:1.0.0",
"attributes": {
"manufacturer": "TT",
"ID": 123456
},
"features": {
"properties": {
"temperature": 20.8,
"humidity": 73,
"barometricPressure": 970.7
}
}
}

you are right thanks ;)

Julian

@JulianFeinauer

yes, its as stated by @ffendt … you shoudl have

{
    "definition": "MM:MMExample:1.0.0",
    "attributes": {
        "manufacturer": "TT",
        "ID": 123456
    },
    "features": {
         "myfeature“: {
             "properties": {
            "temperature": 20.8,
            "humidity": 73,
            "barometricPressure": 970.7
          }
         }
    }
}

ottlukas

@ottlukas

:) yep

Julian

@JulianFeinauer

Hi folks, I made a little Example on how to create a digital twin for a (real) PLC using Apache PLC4X: https://twitter.com/jfeinauer2/status/1217133458872524800

Atul Kumar

@writetoatul_twitter

When connecting to local ditto to local hono: what should be the ID and uri?
in the code snippet here
https://www.eclipse.org/ditto/2018-05-02-connecting-ditto-hono.html

Yannic Klem

@Yannic92

I can't tell you what the URI of your local hono deployment, it's up to how you deployed hono.
Your connection ID must just be unique within your ditto instance. Feel free to choose any ID you like.

Where communities thrive

People

Repo info

Activity