-
Notifications
You must be signed in to change notification settings - Fork 3
IoT Platform Integration
The server can be configured to enable user's devices to publish classification results to IBM's IoT Platform. This then allows other applications to connect to the IoT Platform and subscribe to one or more device's classification results. The event delivered to IOT is in JSON format and looks like the following:
{ "startMsec": 1522926812969, // start time of the sound that was classified "endMsec": 1522926815976, // end time of the sound that was classified "status": "abnormal", // classification of the sound from the 'status' model, which gives 'normal' or 'abnormal' values. "status_confidence": 1, // confidence in the status value. "cause": "silence BEHIND", // classification of the sound from the 'cause' model. "cause_confidence": 1, // confidience in the 'cause' value "normal_confidence": 0, // The status_confidence value if status is normal, otherwise 0. "istatus": 1 // not used anymore }
The server is configured on a per user basis for the IoT - that is, each user can be associated with zero or one IoT platform instance and multiple users can use the same instance if desired. The server is configured in the resources/iotp.properties file or a file pointed to by IOTP_PROPERTIES_FILE environment variable - the latter takes precedence. An IoT platform is configured using the Organization ID, API Key and Authentication Token as defined for the IoT instance to which users will be connecting. The format for an individual instance is as follows:
<orgid>.API-Key=... <orgid>.Authentication-Token=... <orgid>.enabled.users=...