Project Logs

Collapse

• Schemas for everyone~!

  Roman V • 04/26/2017 at 10:28 • 0 comments

  The next project log is still on the way. It's delayed as I'm trying to figure out a problem with data models.

  This project is a mix of software and hardware development. The software part is rather tricky so I'm putting efforts into making the code base modular (or more accurately, making libraries).

  The biggest hurdle I'm facing right now is dealing with JSON Schema. Since each device can have multiple resources, where each resource provides data that is described with one or more JSON schemas. OIC Spec v1.1.0 contains quite an extensive list of schemas for various resources. (doors, heart rate monitors, air conditioners, etc). So I'm deciding on how to deal with them, since vendors may specify their own schemas, it's just becoming a bit of a mess.

  The plan for now will be generating code for the known schemas in OIC spec v1.1.0, whill be some work honestly. but hopefully soon i'll have a nice generic library that is not too complicated to use, which will be extended later on with dynmic things
  

• Where it's at

  Roman V • 04/15/2017 at 23:02 • 0 comments

  Hello World is great and all. But this is where my project sort of kinda explodes into a huge complex mess that's yet to be organsied.

  My next project goal was to control a RGB LED from my phone or desktop.

  • Add a RGB LED resoruce with information about how to send data to it
  • Allow the App to identify the resource's schema and present a UI the easily control the resource.

  Simple enough, right?

  Read more »

• First Steps

  Roman V • 04/14/2017 at 08:32 • 0 comments

  This project has been started already and well, haven't documented anything about it except for what's been posted here.

  My first steps involved having a look at what's already available for IoT from a low level embedded developer point of view. Since I have no commercial background in IoT and wanted to build something for my home.

  First round of researching found an already popular MQTT protocol which is primarily used over TCP. This protocol is a simple Subscribe/Publish messaging protocol with a few added features like passwords and (I think) forwarding messages onto nodes not directly accessible by the subscriber. It's clean, though, not feature rich.

  For some reason I was interested in UDP IoT protocols (possibly for ease of jumping into Low Power mode and not worrying about TCP states). I Quickly found CoAP which was designed to follow in the footsteps of HTTP; As it's designed for low resource environments, includes URI schemes: `coap://` and `coaps://` (using DTLS), oobserve (subscribe) model and a pile of other features.

  Read more »

View all 3 project logs