(DISCUSSION) Implement sensor node type (hook up with backend)

[DasPlankton]

The users should be able to connect sensor to their profile in order to view the sensor data live in the graph.

1) Click on the create node button 2) Enter a title 3) Select sensor node from the node type dropdown 4) Save the new node 5) Open the fullscreen view of the newly created sensor. 6) Open the node menu and copy the node URL 7) Enter the node URL in the sensor (feel free to add more details on this) 8) Once the node receives data, it should display this data in the fullscreen view form (see walkthrough) 9) A history of the received data should ideally be shown in the form of a timeline (let's discuss how many values are being saved in which frequency, what are the min and max values of the timeline?) 10) After closing the fullscreen view, the sensor node should display the value and unit in real-time (see attached walkthrough)

[Pagebakers]

I'm not sure what works has been done on this, since it's both assigned to you axel and isbl, can you unassign or publish the branch if you working on this?

Thanks! :)

[axelchalon]

UI is at https://github.com/jolocom/little-sister/tree/feature/%23201-sensor-node-type but it might not stay this way. There is no backend really (we had the temperature sensor update the RDF file each time), and it wasn't real time on the client as we didn't subscribe to the node with the websockets.

We need to continue talking with the partners (Csaba) before we can go further.

[Joachim16]

@Exulansis we should re-evaluate this issue and adept it to the actual needs of WP3 / WP4

[Joachim16]

yesterday Fabian from Fraunhofer mentioned that the real question for us with Little Sister is if we can stream real time data - since for him or the IoT community in general IoT = real time data in the context of WP3 and WP4 of AGILE I'm moving this issue into the sprint backlog @Exulansis @Pagebakers @rawild

[Pagebakers]

Depends on the throughput, obviously we can't process high velocity data through the solid server, but sensors that update every x seconds should be fine. Also the proxy doesn't support websockets yet, so we can't do it fully realtime until we fix that, we need websocket support for a whole lot more features, improving the performance for example, so we should definitely give this some prio.