Koster: planning to support MQTT and
events/actions
... same Web accessible
... as well as local network
McCool: when you bridge VPN with your
local network
... not tested yet
Koster: next step for checking VPN
... will work a few more hours
McCool: hoping it would work
Koster: ok
... working on TDs and preparation files
McCool: what about OCF?
Koster: can onboard it
McCool: you could try iotivity with
VPN
... I also would check old version of iotivity
... by the end of today, would expect OCF devices will also
work
Koster: yeah
... interesting
... the version I have is OCF 1.1
McCool: we can coordinate with each
other
... I can work with smart home demo for example
... by the end of today, VPN setting will be sorted out
Koster: ok
... wondering how to handle motion sensor
... turn on light and sensor detects it, etc.
... LED behavior will trigger something
... basic stuff going first
... any VPN stuff going now?
McCool: VPN endpoint going on this
side
... server is always 10.8.2.1
... try the VPN and ping the server
... was doing it yesterday
... a bit concerned about timeout
... will find out the reason
... even if it's working technically
Koster: ok
McCool: also test robustness depending on timing
Toumura: no updates here
... just updated nodegen code
... fixed several bugs
... uploaded the fixed version to GH
... if you use it, please update the code
... and rebuild the node
McCool: need one thing to work
... node-red would be good
Yamada: some trouble here
... gateway for real devices has trouble with long-polling
... doesn't work well now
... now I'm investigating the issue
... will inform you all after the trouble is resolved
Toru: maybe related to the issue with the gateway last night
McCool: not related to the VPN service?
Toru: right
McCool: any issues with VPN?
(none)
McCool: need to work for another
assignment till noon JST
... but if any problem with VPN, please let me know
... IRC and email
... bridging should work first
... have to give fixed IP address first
Koster: regular ThingWeb directory?
McCool: unfortunately, the server machine
is broken
... maybe you should go to bed and I'll fix the problem
... will post the IP of the server
... main thing we need to assume is Thing directory is not
available permanently
... your device should remember its IP address
... if the device crashes, OCF server will give different IP
address
Koster: as an application, we need to discover devices
McCool: new OCF installation would be
better
... IP address given depending on the MAC address, it seems
... TDs need to be updated because the IP address are changed
periodically
... if that is a problem, I can fix it
... but we should not assume IP addresses are fixed
... also there is some timing gap, so we should not be too
optimistic about timing
... anything else?
(none)
McCool: next call, I expect Matthias will
be available
... hoping by tomorrow testing environment will be improved
[sep. 26th slot a adjourned; next call at 3pm JST, 8am EU, 11pm US Pacific]