When trying to read a standalone sensor, where the owner is using Neuro-Access, does not work, since the owner interface in the app does not interface the standalone sensor correctly. There are two problems:
The sensor is read by the app (to see what fields are available), as if it was a node behind a concentrator, with an empty Node ID. No Node references must be present in a sensor-data request from a sensor device. This results in a feature-not-imeplemented error from the sensor, as it does not support the concentrator interface. The interface therefore does not show available fields.
When the user selects to approve everything, the approval is done incorrectly. A instruction with an empy JID is provided, instead of an instruction, or a instruction with the Bare JID of the original requestor.
Available information:
i. Video from App
ii. ZIP with three sniffer files in XML (can be viewed as-is, or loaded into the Simple ioT Client from the IoT Gateway repo)
ii.a) Sniffer from client requesting to read via chat interface.
ii.b) Sniffer from sensor
ii.c) Sniffer from app
When trying to read a standalone sensor, where the owner is using Neuro-Access, does not work, since the owner interface in the app does not interface the standalone sensor correctly. There are two problems:
The sensor is read by the app (to see what fields are available), as if it was a node behind a concentrator, with an empty Node ID. No Node references must be present in a sensor-data request from a sensor device. This results in a feature-not-imeplemented error from the sensor, as it does not support the concentrator interface. The interface therefore does not show available fields.
When the user selects to approve everything, the approval is done incorrectly. A instruction with an empy JID is provided, instead of an instruction with the Bare JID of the original requestor.
Available information:
i. Video from App ii. ZIP with three sniffer files in XML (can be viewed as-is, or loaded into the Simple ioT Client from the IoT Gateway repo) ii.a) Sniffer from client requesting to read via chat interface. ii.b) Sniffer from sensor ii.c) Sniffer from app
provisioning in app
sniffers.zip