[NEW FEATURE] Plugins: Monitor The Things Stack LoRaWAN gateways with Ubidots

Ubidots Announcements
, ,
1

Hi there! we’re excited to announce our latest plugin:

image
image850×149 20.2 KB

With this plugin and Ubidots’ drag-n-drop IoT dashboards, you’ll be able to build your own NOC (Network Operating Center) for your LoRaWAN gateways :wink:.

Now, this is not exactly our office, but it’s what having a self-built NOC feels like:

image
image1534×797 431 KB

If you have gateways out in the field, and you’re are wondering whether they are performing right, then this plugin is for you. Check the full guide here.

Troubleshooting
Please note that, for this plugin to work, you need to make sure you’re using a valid TTS API Key. If you can’t see any data or newly created devices, please check your API key using an HTTP client such as Postman, by making a GET request to

URL: https://<YOUR_TTS_SERVER/api/v3/gateways
Method: GET
Auth: Use your TTS API Key in a Bearer token header

You should be getting a successful response like this:

image
image1047×689 86.3 KB

What do you think? How would you expect to be using this plugin? Leave us your comments or ideas below

2

This plugin will be officially released on Tue Jan 26th, in the context of The Things Conference.

3

Hello Ubidots team. This plugin doesn’t show up in the plugin list (anymore).

4

Hello, @marlanw

Thanks for reaching out,

The plug-in is currently unavailable but it will be released soon, after some modifications we have made to improve it get tested. As soon as the new version gets ready for release I will let you know immediately.

Regards,

-Santiago

5

Ok. please don’t prioritize this for me. But it looks like a neat plug-in.

6

This plugin shows up in the “add plugins” dialog/directory as 0.3 version. If it is new, pls let me know, if not, then it probably should be hidden.

7

Hello, @marlanw

I hope this note finds you well,

The TTS account you want to use for the plugin is for a community edition account or a paid TTS license? I’ll be attentive to your comments.

Regards,

-Santiago

8

My TTS is the open source version running on a Linode cloud machine.

9

BTW - I’m not clamouring for this, I’m simply saying if the plugin listed isn’t released it should not be in the list of plugins - see the thread above. Otherwise users get confused.

10

Hello, @marlanw

The plugin 0.0.3 version is going to be replaced soon with a new version but just like the current version, only works for paid TTS licenses, it is not meant to work with the community edition of TTS.

It turns out that back then on Nov 22 last year, there was a problem with the UI that did not show the whole list of plugins available but it was not because the 0.0.3 had been deprecated by then.

Regards,

-Santiago

11

I don’t use EITHER the community version or the paid TTS version.

I’m using the open source TTS.

Marlan

12

ok, thanks for the clarification but we would not like to set any wrong expectations because, the plugin only works for paid TTS licenses.

13

What is technically needed? Is this because the TTS endpoint is hardcoded? Or is it because the TTS server needs to send to an Ubidots endpoint?

Are you aware of the opensource TTS version? I believe it runs the same stack as the TTS commercial versions… except it doesn’t have tenant capability. There are probably a few more differences, but the opensource has quite a bit of capability.

Both of what you call out / the community and enterprise / are both TTS hosted.

But I guess that begs the other question: Is the 0.03 WORKING for TTS enterprise NOW?