Here are a few questions and answers to help you if you get stuck.
Using the Developer Sandbox
- How can I log into my MK:Smart sandbox?
- How can I spin up a Virtual Machine from a template?
- How can I back up a Virtual Machine or its data?
- How can I delete a Virtual Machine and, optionally, its backups?
- How can I spin up an instance of Node-RED?
- How can I use the MK:Smart node in Node-RED?
- Why can't my VM access the Internet?
- Why can't I add a port forwarding rule?
More FAQ will follow soon.
How do I register a new datastream?
See the Creating a New Data Source tutorial.
How do I submit data via the API?
See the Data Providers' API.
- Is there a standard schema for the content of event and sensor datastreams?
Is access over HTTPS supported, or only HTTP?
Yes, HTTPS can also be used to access the API via
/feedIDand is recommended to keep keys more secure.
Is there a way to subscribe to feeds or datastreams so that new values can be received asynchronously without needing to poll the service?
This feature is planned but not yet implemented. It is technically feasible but there is a need to understand what the API should look like to make it attractive/accessible to developers.
Is there a way to configure trigger conditions e.g. when a datastream exceeds a certain value?
This is not supported directly yet, but is being considered for a future release. However, in the meantime, an application can easily monitor a data feed and create its own trigger.
Is there a way to enumerate via the API all the devices created by a specific account?
Via the portal (but not via the API) it is possible for feed creators to see all their feeds. In many cases a feed will be created per sensor (device), however other approaches are possible. In future this could be added to the catalogue search, and MIS about the feeds (e.g. usage statistics) could be added. Access control/security policy must also be addressed.