Are you looking to automatically export your Industrial IoT sensor data from to your favorite online web services and cloud-based drives and folders? Well, you’ve come to the right place.

This article is part of a series we’ve put together about the Export Jobs software feature on Valarm Tools Cloud. In this episode we’ll cover step-by-step instructions on how to configure Export Jobs to send your sensor measurements to your Microsoft OneDrive.

If you’re looking to export to other online, cloud-based storage services like Google Drive or Dropbox, then have a look at our Industrial IoT blog with specific tutorials for those products.

Let’s get started with Export Jobs from to Microsoft OneDrive.

First step – log in to your account and go to your Device Manager.

Verify which device you’d like to use for your sensor data export job. Also make sure you’ve already set up alias nicknames and custom field labels for your device as described in this tutorial.

Next let’s go to the Export Jobs page.

On your Valarm Tools Cloud Device Manager, click the Export Jobs button on the left.

You’ll need to authorize and link your Microsoft OneDrive account with your account using OAuth.

On your Export Jobs page click the Authorize OneDrive button.

You’ll then be taken to Microsoft’s page to sign in to your Microsoft account.

Follow the steps to sign in and then you’re good to go.

After you successfully verify your Microsoft account, you’ll see that the Authorize OneDrive button has changed to a Disconnect OneDrive button on your Export Jobs page.

Now that you’re linked up, click the green button to Create a New Export Job.

In the window for creating a new export job you’ll first set up the Basics.

Use the text fields to enter a name and description for your export job.

You can describe why you’re making this job so that you, your teams, and anyone else in your organization can quickly remember what this Export Job was made for.

Next up is are configuration settings under Data Generation.

For Schedule, we recommend you experiment with using a Manual schedule at first to verify that all of your settings and files and folders are working exactly how you want them. After you’re satisfied with your configuration, then you can use the automatic scheduled export jobs that export your most recent sensor measurements as often as you need, e.g., once an hour or once a day.

When your export job make a new file with your sensor measurements, each piece of sensor data will be time stamped. In your Time Zone drop down menu, you’ll select which you’d like to use for your export job.

If you’re using a Manual export job then you can select a From and To Date Range for which you’d like to export your data. Note that if you’re using a scheduled export job then Valarm Tools will automatically export only the newest data that has been uploaded since the previous export. And also note that export times are UTC, i.e., export jobs set to go once a day will export at midnight 00:00 UTC each day.

For your Source Type you can choose single device to make it easiest for your 1st time in seeing how this software feature works.

With your IoT Device Source you’ll pick which Valarm device’s data you’d like to export with this automatic job.

Output Format gives you the capability of deciding which file format you prefer for your export. You’ve got various options export file format, like:

  • JSON
  • SHEF
  • CSV

Your Output Columns are the custom column / field names that you’ve set up in your Device Manager. These names will be used in your export files as headers / names for each of your sensor fields.

If you’d like to set up Threshold Filtering, check the box and enable it and set up your filter. You can choose filters like less than or greater than. For example, if you’d like to only export sensor reports that have a temperature above or below a certain value, this is your way to do just that.

In your Sort section you can choose how you’d like to order and sort your sensor readings in your output file. Sensor data is sorted by date and you can pick whether you want your IoT data to be sorted in ascending or descending order.

In the final section you’ll configure your Output / Destination.

In this blog post we’re demo’ing Microsoft OneDrive, so we’ll pick that in the Storage Service menu.

If you’d like to save space and bandwidth, you can choose a Compression option. You can pick Gzip or Zip if you’d like to compress. Or you can choose None if you don’t want to use compression.

Type in the Folder / Directory where you’d like to export your sensor data onto your Microsoft OneDrive.

Pick which File Format you prefer to use. You’ll decide whether you want to automatically name your file with the time stamp, date range, IoT device name, or set a custom static file name. Make sure you include any file extensions you configured previously, e.g., if those are the options you chose earlier. See the screenshot for any example.

You’re done configuring your IoT Sensor Data Export Job. Click Save.

You’ll now see your new Export Job in your list of export jobs.

Click Run Now and we’ll make sure everyone is happy with the setup.

After the job runs you’ll see the latest Status Update and Last Run time.

Our Export Job ran successfully, let’s see the results.

After logging in to Microsoft OneDrive, we see the Export Job file we just configured.

When we download, unzip, and open the CSV file in Microsoft Excel we see that all of our IoT sensor data was successfully exported just the way we like it.

That’s your introductory overview of how to use your software features called Export Jobs.

In this story we went through a step-by-step tutorial on how to export to Microsoft OneDrive. Similarly, you can export to other web services like Google Drive, Dropbox, FTP servers, and Amazon S3. Use the other web file services as you need them and see our blog and videos for guides on integrating those platforms.

Please don’t hesitate to get in touch at if you’ve got any questions or would like to see additional IoT software features like integrating more online, cloud-based web file services.