octoblu / issues

The place to report Octoblu issues
3 stars 2 forks source link

Thing options and message schema should be query-able without devince having to be 'online' #208

Open brianehlert opened 9 years ago

brianehlert commented 9 years ago

There should be some way to query the options schema and the message schema of known Things without that Thing having to be online and report it back to Meshblu. Optimally, this would be available through the Meshblu API.

One possible way is that I could create a device of a known type. And then I can query that information back. If the schema have changed, the device will of course update its schema when it comes on-line. At least this way I could have a base set of options and message knowledge about the device without requiring that the device be installed and running.

Another possible way would be a query for the options / message schema of known device types. Without having to create those devices. More like; "Meshblu is aware of all of these device types and here are their known properties."

iamruinous commented 9 years ago

My goal is to solve this problem by creating a device and node registry service where you can add your own devices and nodes (for flows). That would give you a place to query the schema of a particular type of device. The device entry in the registry would serve as a "template" for any new devices of that type.

Octoblu would then use this registry to query any devices that you have access to and use that to create the new device in Meshblu. This also allows for private APIs and device types.