McCool: something is still
wrong
... will work on that
... more work tomorrow
... my CoAP devices on VLAN difficult to use
... went through and cleaned up my TDs
McCool: updated my proxy
[[
"href": "http://upsq0.local:8085/api/say",
]]
McCool: for actions to "say"
... my camera has "crop" action
... input/output are different
... wondering how to deal with that pattern
... will dig up right TDs
[[
]]
McCool: currently using HTTP
... but would use HTTPS
[[
"iot": "http://iotschema.org/",
"http": "http://www.w3.org/2011/http#"
]]
McCool: the above two seems to work
now
... use POST for write/update
[[
"rel": "invokeaction",
"http:methodName": "POST"
]]
Koster: "rel" should be there
... we have default
McCool: above TD has 21 devices
Koster: I'd like one pager now
McCool: straight down OAuth for TPAC
Koster: have MQTT device
... light and light sensor
... get MQTT notification for light sensor
McCool: who would do another JS
thing?
... turn light on/off
Kaz: maybe Toumura-san?
Koster: have some timing to
work
... that's working at least on my illumination sensor
... next work for VPN
... it's critical to get VLAN going
... we can build the VPN client into the device
... but not use case for us
... we need DHCP, etc.
... should list what we need
McCool: maybe Nakagawa-san is
interested
... people from Intel also
Koster: this is forIETF forks
... working on VPN
McCool: can forward Nakagawa-san's stuff
Koster: OCF devices working
... native CoAP stuff to be done
... illumination sensor, motion sensor
... will share my codes
... not to be done today, though
McCool: are you taking pictures?
Koster: will do
McCool: please take pictures
Sano: connected devices via
proxy
... SmartThings light
... Eurecom
... Intel
... could get connected
... also tried Oracle
... but couldn't handle the URL since it was %_encoded
... Nakagawa-san reported that node-red direct connection
Itaru: wot client by node-red
... tested all vendors at least with one for each
... right now it's too detail to report
... would like to contact each person to make it clear
McCool: would follow up via F-Interop?
Itaru: tested site-to-site connection
... it's not internet-wide test
... some difference
... there is some information
... might be useful for McCool
McCool: Michael Koster and myself would follow the instruction
Itaru:local testbed network
... client-to-client directly using openvpn configuration
... good for our test bed
... that's local one using DHCP
... we can get IP addresses by that
Kaz: question about F-Interop
McCool: somebody need to provide
information
... multiple people should do that
Koster: was kind of concerned
Kaz: at the moment, F-Interop itself is not included here. right?
McCool: right
Kaz: we should talk with Dave, Federico, Ege, etc., who are working on that
Koster: Federico gave some message
Kaz: wondering if their mechanism would be really reusable for our purposes
Koster: wondering about VLAN,
etc.
... custom server for DHCP, etc.
McCool: we don't really need great scalability ourselves
Koster: we can have port filtering,
etc.
... or switching network
Lagally: working on node-wot
... bridge servient capable JS script
... bridging different networks
... trying to get a bridge into Panasonic
... good to see messages
... not yet done
... also Siemens festplan
... earlier question today
McCool: Matthias is not available today
Lagally: also worked with speech
service from Intel
... but got message like "not found"
McCool: have to post message to
"portal.mmccool.net:29453/say"
... would look into it
... string in quotes?
... double quote + string + double quote
Lagally: can share my screen?
McCool: sure
Lagally: sending PUT this URL
... (shows his Postman UI)
... used PUT
McCool: please try POST instead
... and "api/say"
(and it works!)
McCool: need to fix the URL within TD (and add "api/")
Lagally: ok
... and working a bit longer today
... turn on light in Osaka by Panasonic
Toumura: (share screen)
... (node-red ui)
... intel and oracle simulator
... some sample app connected to...
... industry use case monitoring bug
... provided by Oracle simulator
... in normal situation, monitoring output temperature
... shows Panasonic bulletin board
... (shows Oracle digital twin simulator UI)
... tried to send message to Fujitsu's lamp
... but wrong URL
... now it works ok
McCool: can you take screen shot?
Toumura: yes
Kaz: so connected to
Panasonic
... but not Fujitsu?
Toumura: rotary beacon not connected
Sano: sorry it's not working now
McCool: pretty sexy
Toumura: tx
<mlagally> Lagally: we keep the simulators and cloud service instance up and running until Lyon
Lagally: if anybody wants to continue to use oracle simulator, please do so
Matsukura: Sano-san and Nakagawa-san have already made report
Yamada: (share screen)
... node-red UI
... triggering sensor is done
... cleaning up is done
... turn on MQTT done
... turn off light done
... these 3 (close window blinds, turn on surveillance camera,
control other devices)
Kaz: 3rd one means collaboration with Toumura-san's app?
Yamada: yes
... in the future
McCool: tx
... it's late night in Japan
... still need to work more
... personally will keep working for Lyon
... we've got a lot of progress
Kaz: so people are encouraged to
generate summary reports from this online plugfest effort
... and we can check the progress and next step during the
upcoming PF call on Oct 3
[online plugfest adjourned; people can continue to use this webex for a while if needed; also can talk with each other on this IRC channel]