diff --git a/cdk/lambda/index.js b/cdk/lambda/index.js index 17503e4b..d8a589e1 100644 --- a/cdk/lambda/index.js +++ b/cdk/lambda/index.js @@ -421,8 +421,6 @@ exports.handler = async (event) => { "/docs/tagoio/getting-started/how-it-works", "/portal/en/kb/articles/7-beagle-bone-black": "/docs/tagoio/tutorials/beagle-bone-black", - "/portal/en/kb/articles/75-thinxtra-xkit-for-sigfox": - "/docs/tagoio/tutorials/thinxtra-xkit-for-sigfox", "/portal/en/kb/articles/8-raspberry-pi": "/docs/tagoio/tutorials/raspberry-pi", "/portal/en/kb/articles/83-connecting-zen15-power-using-smartthings-hub": @@ -526,8 +524,6 @@ exports.handler = async (event) => { "/portal/en/kb/articles/tagoio-mqtt-relay": "/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio", "/portal/en/kb/articles/tags": "/docs/tagoio/getting-started/tags-system", - "/portal/en/kb/articles/ticket-severity-options": - "/docs/tagoio/support/ticket-severity-options", "/portal/en/kb/articles/trigger-by-geofence": "/docs/tagoio/actions/trigger-by-geofence", "/portal/en/kb/articles/trigger-by-usage-alert": diff --git a/docs/api/login-as-user.api.mdx b/docs/api/login-as-user.api.mdx index 58a9c3bd..5ffb82df 100644 --- a/docs/api/login-as-user.api.mdx +++ b/docs/api/login-as-user.api.mdx @@ -1,7 +1,7 @@ --- id: login-as-user title: "Get User Token" -description: "Get TagoRUN User Token and allow to perform request to TagoRUN specific endpoints (not available)." +description: "Get TagoRUN User Token and allow performing requests to TagoRUN specific endpoints (not available)." sidebar_label: "Get User Token" hide_title: true hide_table_of_contents: true diff --git a/docs/api/tagoio-api.info.mdx b/docs/api/tagoio-api.info.mdx index 5c51df09..e887628b 100644 --- a/docs/api/tagoio-api.info.mdx +++ b/docs/api/tagoio-api.info.mdx @@ -34,11 +34,11 @@ The documentation is split by which token you're required to use in the request. TagoIO provides 4 different tokens: - **Device-Token**: The token from your device, which you can get from the device's page. -- **Profile-Token**: Also know as Account-Token. You get from your profile settings page. +- **Profile-Token**: Also known as Account-Token. You can retreive this from your profile settings page. -- **Network-Token**: Is the token from your Network. Only available if you're owner of the network in your integrations page. +- **Network-Token**: This is the token from your Network. Only available if you're the owner of the network in your integrations page. -- **Analysis-Token:** The token from your analysis, available in the analysis page. +- **Analysis-Token:** The token from your analysis, available on the analysis page. --- #### Setting the API Endpoint Region When making a request to the TagoIO API, you must also specify the appropriate regional endpoint. Choose one of the following endpoints based on your geographical region: @@ -52,7 +52,7 @@ When making a request to the TagoIO API, you must also specify the appropriate r **URL:** `https://api.eu-w1.tago.io/` - **Tago Deploy:** - You should use your own API URL that is available in your Domains section of the TagoDeploy. + You should use your own API URL that is available in the Domains section of TagoDeploy.
You can use payload fields in the HTTP endpoint, like the example above but > with a variable (`https://myapi.io/endpoint/$VALUE$`), or even in the HTTP > Headers like in the example below: -![Image 16](/docs_imagem/tagoio/1628001652255-dcw.png) +![Image 16](/docs_imagem/tagoio/rounded-image-1767014631018.png) The `TagoIO-Retries` header is managed by the TagoIO API and sent in every Post request for this Action type, and indicates the number of attempts to post the @@ -223,7 +231,7 @@ fails to receive it. To set up a fallback device, enable it in the bottom part of the HTTP Post action settings and put the token for the device you intend to hold the data. -![Image 17](/docs_imagem/tagoio/1628001764337-3t4.png) +![Image 17](/docs_imagem/tagoio/rounded-image-1767014751312.png) After 10 unsuccessful attempts, the data will be sent to the fallback device with some information added to the `metadata` in the `_http_*` properties @@ -254,6 +262,8 @@ with some information added to the `metadata` in the `_http_*` properties This option is only available if your Action is of the type **MQTT Topic**. This action will insert the data directly into the device's data storage. +![Insert to Device's data storage action configuration](/docs_imagem/tagoio/rounded-image-1767014904194.png) + ## Message Variables In some action types, the message body can be as simple as a text like _Hi, your diff --git a/docs/tagoio/actions/index.md b/docs/tagoio/actions/index.md index 0d2e193f..a89a9401 100644 --- a/docs/tagoio/actions/index.md +++ b/docs/tagoio/actions/index.md @@ -19,11 +19,11 @@ Learn about [Defining Actions](/docs/tagoio/actions/defining-actions.md). To create a new Action, click the "Action" button in the sidebar, then click the + button in the top right. -![Actions screen showing the Add Action button and Actions list](/docs_imagem/tagoio/actions-2.png) +![Actions screen showing the Add Action button and Actions list](/docs_imagem/tagoio/rounded-image-1769103195000.png) ### Type of trigger -There are 5 types of triggers you can use: +There are 6 types of triggers you can use: * **Variable** – The action will be triggered when one variable meets certain conditions. If your device has sent data and the variables are meeting those conditions, this action will be triggered. Learn more about [Trigger by Variable](/docs/tagoio/actions/trigger-by-variable.md). @@ -35,5 +35,11 @@ There are 5 types of triggers you can use: * **Geofence** – This action will be triggered whenever a variable containing location data meets specific geofence conditions—either inside or outside a predefined area. Learn more about [Trigger by Geofence](/docs/tagoio/actions/trigger-by-geofence.md). +* **MQTT Topic** – This action will be triggered when a message is received on an MQTT topic. Learn more about [Trigger by MQTT Topic](/docs/tagoio/actions/trigger-by-mqtt-topic.md). + +:::warning +Note that the **TagoIO MQTT Broker** is available exclusively for Starter and Scale accounts in the US database region. Free accounts and accounts hosted in the European database region may use third-party MQTT services with TagoIO via the [MQTT Relay](/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio.md) feature. +::: + To prevent your action from continuously activating when a trigger condition is met, it is advisable to define a reset trigger condition. Ensure you check the “[Trigger Unlock]” option to avoid potential issues with your logic and account: [Trigger Unlock](/docs/tagoio/actions/trigger-unlock.md). diff --git a/docs/tagoio/actions/running-analysis-via-action.md b/docs/tagoio/actions/running-analysis-via-action.md index 29150902..e470f20c 100644 --- a/docs/tagoio/actions/running-analysis-via-action.md +++ b/docs/tagoio/actions/running-analysis-via-action.md @@ -17,12 +17,12 @@ To run an Analysis from an Action: 2. Set the field "Type of action" to "Run Analysis". 3. Select one or more Analyses to run. -![Action Run Analysis UI](/docs_imagem/tagoio/running-analysis-via-action-2.png) +![Action Run Analysis UI](/docs_imagem/tagoio/rounded-image-1767033430352.png) Notes about the UI shown above: - The "Type of action" field should be set to "Run Analysis". - Use the "Run one or more analyses" area to add the Analyses you want to execute (e.g., Analysis 1, Analysis 2). -- Use the plus (+) and minus (−) controls to add or remove Analyses from the Action's list. +- Use the plus and trash can icons to add or remove Analyses from the Action's list. - You can specify up to **10 Analyses** that will run in parallel when the Action is triggered. ## Action Context Variables diff --git a/docs/tagoio/actions/trigger-by-geofence.md b/docs/tagoio/actions/trigger-by-geofence.md index 222c29c7..edfbf5b4 100644 --- a/docs/tagoio/actions/trigger-by-geofence.md +++ b/docs/tagoio/actions/trigger-by-geofence.md @@ -10,11 +10,11 @@ The “Trigger by Geofence” feature allows you to execute an [Action](/docs/ ## Setting the Trigger Conditions To set up this trigger, you need to draw geofences on the map. Geofences can be either polygons or circles, and you must select a variable that contains the location data. -For each condition you can only set one geofence, so if you need multiple geofences you will have to create additional conditions—up to 10 in total. +For each condition, you can only set one geofence, so if you need multiple geofences, you will have to create additional conditions—up to 10 in total. You must define whether the trigger should activate when the chosen variable is **inside** or **outside** the geofence. When the selected variable receives new location data, the system checks if this location meets the specified geofence condition. -![Image 2](/docs_imagem/tagoio/external-bef9d9d6.png) +![Image 2](/docs_imagem/tagoio/external-notanymore.gif) ### Editing Geofence diff --git a/docs/tagoio/actions/trigger-by-mqtt-topic.md b/docs/tagoio/actions/trigger-by-mqtt-topic.md index 22d5eec7..aadbeea0 100644 --- a/docs/tagoio/actions/trigger-by-mqtt-topic.md +++ b/docs/tagoio/actions/trigger-by-mqtt-topic.md @@ -12,7 +12,7 @@ messages are published to the topics they are subscribed to. To learn more about the MQTT infrastructure used by TagoIO, see [MQTT](/docs/tagoio/integrations/networks/mqtt/mqtt.md). -:::info +:::warning The TagoIO MQTT Broker is available exclusively for Starter and Scale accounts in the US database region. Free accounts and accounts hosted in the European @@ -31,7 +31,7 @@ There are 2 categories for this trigger type: that device will be tested against your topics to determine whether this action should be triggered. - ![Single-device selection UI](/docs_imagem/tagoio/trigger-by-mqtt-topic-2.png) + ![Single-device selection UI](/docs_imagem/tagoio/rounded-image-1767016336359.png) 2. **Multiple devices**\ Allows you to watch multiple devices. Any data sent by those devices will be @@ -39,14 +39,14 @@ There are 2 categories for this trigger type: triggered. For this type, you must supply the tag keys and tag values of the devices you want to watch. - ![Multiple-devices tag selection UI](/docs_imagem/tagoio/trigger-by-mqtt-topic-2.png) + ![Multiple-devices tag selection UI](/docs_imagem/tagoio/rounded-image-1767016364577.png) ## Trigger Conditions After setting up the device, you should set a condition for your action to be executed. To do so, you must head over to the **Trigger** section. -![Image 4](/docs_imagem/tagoio/1588075755429-J4Y.png) +![Image 4](/docs_imagem/tagoio/rounded-image-1767016482525.png) For each row, you need to set the topic that will be listened to. You may use MQTT [wildcards](/docs/tagoio/integrations/networks/mqtt/mqtt.md) for the topic if @@ -56,9 +56,13 @@ You can set multiple conditions in an action; if at least one of them results in a match, the action will be executed. :::info +When you set up multiple conditions, the action will execute only once per MQTT +message, even if that message matches multiple conditions. For example, if you +have two conditions: -Note that setting up multiple conditions will execute the action only once if -any of the conditions are matched. This means that if you send two variables -that would trigger the action at the same time, it will only trigger one action. +- Condition 1: Topic `sensors/+/temperature` +- Condition 2: Topic `sensors/+/+` +And you receive a message on topic `sensors/device1/temperature`, it matches +both conditions, but the action will trigger only once for that single message. ::: diff --git a/docs/tagoio/actions/trigger-by-resource.md b/docs/tagoio/actions/trigger-by-resource.md index 84b8a464..74e7306d 100644 --- a/docs/tagoio/actions/trigger-by-resource.md +++ b/docs/tagoio/actions/trigger-by-resource.md @@ -19,11 +19,11 @@ After setting up the device, you should set a condition that causes your Action :::tip -You can set multiple conditions in an Action. If at least one condition matches, the Action will be executed. +You can set multiple conditions for different resource types in a single Action. If at least one condition matches, the Action will be executed. ::: -![Trigger panel — "If one of the conditions match, the action will be triggered."](/docs_imagem/tagoio/trigger-by-resource-2.png) +![Trigger panel — "If one of the conditions match, the action will be triggered."](/docs_imagem/tagoio/rounded-image-1767016776767.png) 1. **Resource** – Select a resource to be tested. 2. **Tag key** – The tag key of the resource to be tested. diff --git a/docs/tagoio/actions/trigger-by-schedule.md b/docs/tagoio/actions/trigger-by-schedule.md index 182393cf..5161bc52 100644 --- a/docs/tagoio/actions/trigger-by-schedule.md +++ b/docs/tagoio/actions/trigger-by-schedule.md @@ -10,12 +10,12 @@ There are two categories within this trigger type: 1. By Interval Allows you to specify a time interval to trigger the Action automatically. Choose the time interval on the right side of the interface; the minimum allowed time is 1 minute. - ![By Interval selector showing an interval selection (e.g., 15 Minutes)](/docs_imagem/tagoio/trigger-by-schedule-2.png) + ![By Interval selector showing an interval selection (e.g., 15 Minutes)](/docs_imagem/tagoio/rounded-image-1767018081996.png) 2. By Date Allows you to specify a date or a recurring date rule to trigger the Action. For example, you can choose to run an Action on the second Wednesday of each month. - ![By Date selector showing date-based scheduling options](/docs_imagem/tagoio/trigger-by-schedule-2.png) + ![By Date selector showing date-based scheduling options](/docs_imagem/tagoio/rounded-image-1767018166748.png) ## Customizing By Date diff --git a/docs/tagoio/actions/trigger-by-usage-alert.md b/docs/tagoio/actions/trigger-by-usage-alert.md index 1e30b5da..ee55d98a 100644 --- a/docs/tagoio/actions/trigger-by-usage-alert.md +++ b/docs/tagoio/actions/trigger-by-usage-alert.md @@ -3,21 +3,42 @@ title: "Trigger by Usage Alert" description: "This article explains how the \"Trigger by Usage Alert\" feature works, lists which TagoIO resources and services can fire usage alerts, and describes how to define the conditions that trigger an action." tags: ["tagoio"] --- -The “Trigger by Usage Alert” feature lets you execute an Action when a specific service or resource meets predefined usage conditions. Below is a list of Resources and Services that can be used to trigger an Action. +The "Trigger by Usage Alert" feature lets you execute an Action when a specific service or resource meets predefined usage conditions. ## Resources and Services -| Resources | Services | -|---|---| -| [Access Management](/docs/tagoio/tagorun/access-management/) | [Input](/docs/tagoio/profiles/services/data-input-service.md) | -| [Actions](/docs/tagoio/actions/) | [Output](/docs/tagoio/profiles/services/data-output-service.md) | -| [TCore](/docs/tagocore/) | [Analysis](/docs/tagoio/analysis/) | -| [Device](/docs/tagoio/devices/) | [Data Records](/docs/tagoio/profiles/services/data-records.md) | -| [Team Members](/docs/tagoio/profiles/team-management-sharing-your-profile.md) | [SMS](/docs/tagoio/profiles/services/sms-service.md) | -| [Dashboards](/docs/tagoio/dashboards/) | [Emails](/docs/tagoio/profiles/services/e-mail-service.md) | -| [Analysis](/docs/tagoio/analysis/) | [Run Users](/docs/tagoio/profiles/services/end-users-service.md) | -| | [Push Notifications](/docs/tagoio/profiles/services/notification-service.md) | -| | [File Storage](/docs/tagoio/profiles/services/file-storage-service.md) | +The following resources and services can be used to trigger an Action: + +
+
+ +### Resources + +- [Access Management](/docs/tagoio/tagorun/access-management/) +- [Actions](/docs/tagoio/actions/) +- [TCore](/docs/tagocore/) +- [Device](/docs/tagoio/devices/) +- [Team Members](/docs/tagoio/profiles/team-management-sharing-your-profile.md) +- [Dashboards](/docs/tagoio/dashboards/) +- [Analysis](/docs/tagoio/analysis/) + +
+
+ +### Services + +- [Input](/docs/tagoio/profiles/services/data-input-service.md) +- [Output](/docs/tagoio/profiles/services/data-output-service.md) +- [Analysis](/docs/tagoio/analysis/) +- [Data Records](/docs/tagoio/profiles/services/data-records.md) +- [SMS](/docs/tagoio/profiles/services/sms-service.md) +- [Emails](/docs/tagoio/profiles/services/e-mail-service.md) +- [Run Users](/docs/tagoio/profiles/services/end-users-service.md) +- [Push Notifications](/docs/tagoio/profiles/services/notification-service.md) +- [File Storage](/docs/tagoio/profiles/services/file-storage-service.md) + +
+
For example, you can configure an Action to trigger when Analysis usage reaches a specified threshold. Once that threshold is met, a notification can be sent to the profile administrator. @@ -25,7 +46,7 @@ For example, you can configure an Action to trigger when Analysis usage reaches To set up an alert, define the conditions that will trigger the Action. You can specify multiple conditions; the Action will be executed if any one of them is met. -![Image 1](/docs_imagem/tagoio/external-17f4f80c.png) +![Image 1](/docs_imagem/tagoio/rounded-image-1767028703029.png) 1. **Select a Resource or Service:** Choose the specific resource or service you want to monitor as a trigger. 2. **Define Condition and Percentage:** Specify the condition that needs to be met for the action to be triggered, and determine the usage percentage that will activate the trigger. diff --git a/docs/tagoio/actions/trigger-by-variable.md b/docs/tagoio/actions/trigger-by-variable.md index 3dd779f1..9f37af46 100644 --- a/docs/tagoio/actions/trigger-by-variable.md +++ b/docs/tagoio/actions/trigger-by-variable.md @@ -10,14 +10,16 @@ There are 2 categories inside this trigger type: ## 1. Single device Allows you to watch a specific device from your device list. Any data sent by that device will be tested against your conditions to determine whether the action should be triggered. -![Single device vs Multiple devices selection](/docs_imagem/tagoio/trigger-by-variable-2.png) +![Single-device selection UI](/docs_imagem/tagoio/rounded-image-1767016336359.png) ## 2. Multiple devices Allows you to watch multiple devices. Any data sent by those devices will be tested against your conditions to determine whether the action should be triggered. For this type, you must supply the tag key and tag value of the devices you want to watch. -![Selecting tags for multiple devices (tag_key / tag_value)](/docs_imagem/tagoio/trigger-by-variable-2.png) + ![Multiple-devices tag selection UI](/docs_imagem/tagoio/rounded-image-1767016364577.png) -It's important to note that only the Single device category allows you to set Trigger Unlock conditions. To learn more, see [Trigger Unlock](/docs/tagoio/actions/trigger-unlock.md). +:::warning +Note that only the **Single device** category allows you to set **Trigger Unlock** conditions. To learn more, see [Trigger Unlock](/docs/tagoio/actions/trigger-unlock.md). +::: ## Trigger Conditions @@ -26,9 +28,15 @@ After setting up the device, you should set a condition for your action to be ex You can set multiple conditions in an action; if at least one of them results in a match, the action will be executed. :::info +When you set up multiple conditions, the action will execute only once per data +message, even if that message matches multiple conditions. For example, if you +have two conditions: -Notice that setting up multiple conditions will execute the action only once if any of the conditions are matched. This means that if you send two variables that would trigger the action at the same time, it will only trigger one action. +- Condition 1: Variable `temperature` is greater than `25` +- Condition 2: Variable `temperature` is greater than `20` +And you receive a message with `temperature` set to `30`, it matches both +conditions, but the action will trigger only once for that single message. ::: 1. **Select a variable**: Choose a variable to be tested. This will be one of the variables that will be compared against the data from the device. diff --git a/docs/tagoio/actions/trigger-unlock.md b/docs/tagoio/actions/trigger-unlock.md index e255c62b..4f3b0dfb 100644 --- a/docs/tagoio/actions/trigger-unlock.md +++ b/docs/tagoio/actions/trigger-unlock.md @@ -21,7 +21,7 @@ You can check if your action is locked by looking at the **Locked** switch, as s The lock button will only appear once you add at least one condition. -![Image 1](/docs_imagem/tagoio/external-4f45b6c0.png) +![Image 1](/docs_imagem/tagoio/rounded-image-1767030524609.png) ### Manual Locking @@ -31,7 +31,7 @@ You can also set this Locked parameter manually; all you have to do is click it Additionally, you can run the action again when an unlock condition is met. For example, if you are triggering an [Analysis](/docs/tagoio/analysis/creating-analysis.md)​ to set a device in alert mode due to high-temperature readings, you can also switch to safe mode upon meeting an unlock condition. -![Image 2](/docs_imagem/tagoio/external-205c14dd.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1769103607957.png) ### Duplicate Trigger Warning diff --git a/docs/tagoio/addons/control-tower.md b/docs/tagoio/addons/control-tower.md index a986dc59..dfda852d 100644 --- a/docs/tagoio/addons/control-tower.md +++ b/docs/tagoio/addons/control-tower.md @@ -19,7 +19,7 @@ Once you activate Control Tower, you can view data input and output statistics f You can monitor the statistics by going to your Devices module on your Admin and selecting the device you want to visualize: -![Control tower overview](/docs_imagem/tagoio/ctower_device_statistics.png) +![Control tower overview](/docs_imagem/tagoio/rounded-image-1765199046181.png) :::info @@ -42,12 +42,12 @@ You can apply a soft rate limit to: - **Your whole profile** – all devices in the profile follow this limit. To set it, navigate to your Admin page → [Profiles & Teams](https://admin.tago.io/profile) → “More” tab. -![Control tower profile](/docs_imagem/tagoio/profile_limit_ctower.png) +![Control tower profile](/docs_imagem/tagoio/rounded-image-1765199260734.png) - **A specific device** – overrides the profile limit for that device. To set it, go to the [Devices](/docs/tagoio/devices/) module, select the desired device, and click the “More” tab. -![Control tower device](/docs_imagem/tagoio/device_limit_ctower.png) +![Control tower device](/docs_imagem/tagoio/rounded-image-1765199355157.png) :::info @@ -60,8 +60,7 @@ For example: if the hard limit of your plan is 5,000 , even if the soft limit is A significant feature provided by the Control Tower is the capability to access detailed statistics on Hard Limits through your Admin page. Upon activating the add-on, data regarding your requests will begin to be recorded and presented on the [Hard Limits > Requests page](https://admin.tago.io/limits/hard). This enables you to view the current, highest, lowest, and average usage of each hard limit. Furthermore, it allows for the display of advanced statistics, offering a historical view of your usage. - -![Control tower advanced statistics](/docs_imagem/tagoio/rpm_list_advanced_statistics.png) +![Control tower advanced statistics](/docs_imagem/tagoio/rounded-image-1761140461575.png) In the advanced statistics view, you have the option to filter your usage by date and time, as well as to view only the highest, average, and lowest usage. This is beneficial for understanding how your application is performing and determining if any actions are necessary to mitigate the usage of your hard limits. diff --git a/docs/tagoio/analysis/console-for-debug.md b/docs/tagoio/analysis/console-for-debug.md index 59ee02ed..ce35c448 100644 --- a/docs/tagoio/analysis/console-for-debug.md +++ b/docs/tagoio/analysis/console-for-debug.md @@ -3,20 +3,25 @@ title: "Console for Debug" description: "A short guide explaining how to use the Analysis console to monitor script variables, view errors and log output, and clear the console in TagoIO." tags: ["tagoio"] --- -Use the console to monitor the variables and status of your script. You can see any error or text generated by console.log (or context.log). This console is a simple and useful debugging tool. +Use the console to monitor the variables and status of your script. You can see any errors or text generated by console.log (or context.log). This console is a simple and useful debugging tool. ## Console UI -![Console view showing the Console tab and Clear Console button](/docs_imagem/tagoio/console-for-debug-2.png) +![Console view showing the Console tab and Clear Console button](/docs_imagem/tagoio/rounded-image-1761143169484.png) -- Tabs available: General Information, Environment variables, Console, Examples, Tags, More. -- Console area: displays errors and any output generated by your script. -- Clear Console button: clears all output shown in the console area. +- Console Area: displays errors and any output generated by your script. +- Clear Button: clears all output shown in the console area. +- Download Button: downloads the console output as a text file. + +:::tip +The **TagoAI Assistant** can also be used to debug your script by asking about errors or unexpected behavior using the Analysis console. +::: ## How it works -1. Console screen: Any error or response generated by console.log (or context.log) will appear here. +1. Console Screen: any errors or responses generated by console.log (or context.log) will appear here. 2. Clear Console: clears everything currently shown in the console screen. +3. Download Console: downloads the console output as a text file. ## Example @@ -26,4 +31,4 @@ Use console.log in your Analysis script to write to the console: console.log('Debug message:', myVariable); ``` -Learn more about [Analysis](/docs/tagoio/analysis/). \ No newline at end of file +You can learn more about Analysis [here](/docs/tagoio/analysis/). \ No newline at end of file diff --git a/docs/tagoio/analysis/creating-analysis.md b/docs/tagoio/analysis/creating-analysis.md index f24600ae..27684196 100644 --- a/docs/tagoio/analysis/creating-analysis.md +++ b/docs/tagoio/analysis/creating-analysis.md @@ -4,9 +4,9 @@ description: "This article explains how to create a new Analysis in TagoIO, incl tags: ["tagoio", "analysis"] sidebar_position: 1 --- -Creating your own analysis is easy. First, click on **Analysis** in the sidebar, then click the **+ Add Analysis** button in the upper‑right of the Analysis main screen. Enter a name and configure the options described below to create your analysis. +Creating your own analysis is easy. First, click on **Analysis** in the sidebar, then click the **+ New Analysis** button in the upper‑right of the Analysis main screen. Enter a name and configure the options described below to create your analysis. - +![New Analysis Form](/docs_imagem/tagoio/rounded-image-1761141519422.png) ## Name This is the identifier for your analysis. You can use whitespace, numbers, and any other characters in this field. Choose a descriptive name that explains the purpose of the code. @@ -18,7 +18,7 @@ Select the runtime environment for your analysis. An example shown in the dialog Currently supported runtimes include **Deno**, **Python**, and **Node.js** if you run your script on TagoIO. -## Run this script from +## Run this script on Choose where the analysis will run: - **TagoIO** — Edit and run the script directly on TagoIO. - **External** — Run the script on your own computer or server. @@ -35,25 +35,14 @@ When changing between External mode and TagoIO mode, the Analysis Token will be ::: ## Code example -You can optionally start your analysis from a code example template. The Add Analysis dialog includes a dropdown to choose a code example. If you don't want a template, select **No, thanks**. +You can optionally start your Analysis from a code example template. The Add Analysis dialog includes a dropdown to choose a code example. If you don't want a template, you can ignore this field. :::tip -It is highly recommended for beginners to use a real‑world example, as it provides insight into the functions and scopes of the script. +It is highly recommended for beginners to use an Analysis template, as it provides insight into the functions and scopes of the script. You can only select one of these code examples if you are running your script on TagoIO. ::: ## Other fields -The Add Analysis dialog also shows: -- A **“Learn more”** link (for additional guidance). -- Buttons to **“Cancel”** or **“Create my Analysis”** once you have configured the fields. - -After creating the analysis you can open the Script Editor to add and manage the analysis code, adjust environment variables, and configure distribution or external execution as needed. - -### Time interval -You can trigger your analysis script manually, but you can also define a time interval to automatically trigger it. In this field you will find a couple of predefined time options, and you can set your own custom time interval by selecting the **Custom** option. - -### Analysis Token -This field is only used if you are running your analysis as **external**. If you want more information on how the token works, check out the article -[Running Analysis as External using Node.JS](/docs/tagoio/analysis/running-analysis-as-external-using-nodejs.md). +After creating the analysis you can open the [Script Editor](/docs/tagoio/analysis/script-editor.md) to add and manage the analysis code, adjust environment variables, and configure distribution or external execution as needed. diff --git a/docs/tagoio/analysis/distributing-analysis.md b/docs/tagoio/analysis/distributing-analysis.md index 18a0457c..16adbb6d 100644 --- a/docs/tagoio/analysis/distributing-analysis.md +++ b/docs/tagoio/analysis/distributing-analysis.md @@ -3,16 +3,17 @@ title: "Distributing Analysis" description: "This article explains how to distribute a copy of an Analysis in TagoIO by sending a customized install link so others can add and edit their own copy without affecting yours." tags: ["tagoio", "analysis"] --- -You can create a copy of your analysis and send a link to anyone so they can add a copy to their account through a customized install page. Recipients can edit the analysis as they wish. +You can distribute your Analysis by generating a shareable link that lets others install their own copy through a customized install page. Each recipient gets a completely independent copy in their TagoIO account, which they can freely edit without impacting your original Analysis. > Others will be able to edit the analysis that they received without impacting yours. -When other users access the link you sent, they will see a screen like the one shown below. The images and text on that install page are fully customizable. +When other users access the link you sent, they will see a screen similar to the one shown below. The images and text on that install page are fully customizable. -![Map pin example](/docs_imagem/tagoio/distributing-analysis-2.png) -To distribute an analysis, first click in the analysis menu of your admin panel, then select the desired analysis. -Now head over to the distribute section of your analysis by clicking on the **Distribute** tab. +To distribute an analysis, first click on the analysis menu of your admin panel, then select the desired analysis. +Now navigate to the distribute section of your analysis by clicking on the **Distribute** tab. + +![Map pin example](/docs_imagem/tagoio/rounded-image-1761144346438.png) The **Distribute** function relies on creating a customized install page for anyone to install a copy of your analysis. To tailor this page you can modify the title, logo and main image in the corresponding fields. At the bottom of the page there is also a section where you can set values for the copy’s environment variables; these default to the values defined in your own environment but can be changed without affecting your original settings. diff --git a/docs/tagoio/analysis/environment-variables.md b/docs/tagoio/analysis/environment-variables.md index 1938286f..53d8501e 100644 --- a/docs/tagoio/analysis/environment-variables.md +++ b/docs/tagoio/analysis/environment-variables.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- Environment variables let you pass values into the execution context of your Analysis script. Use them to store tokens, account IDs, device IDs, or any other values that the script will use at runtime. The Analysis retrieves these values as environment parameters and exposes them to your code via the `context.environment` global object. - +![Environment Variables](/docs_imagem/tagoio/rounded-image-1761143952960.png) ## How to use Environment Variables diff --git a/docs/tagoio/analysis/index.md b/docs/tagoio/analysis/index.md index 91751f89..0f5af254 100644 --- a/docs/tagoio/analysis/index.md +++ b/docs/tagoio/analysis/index.md @@ -80,7 +80,7 @@ Here’s the short path to get an Analysis running: In your Admin, go to the [Analysis module](https://admin.tago.io/analysis), create an analysis and choose a runtime: Deno, Node.js, or Python based on your stack and dependency needs. 2. **Grant the needed permissions to your analysis.** - When you create an analysis, it doesn’t have the needed permissions to access data or run services. For that reason, you need to generate a policy that gives access only to operations and data within scopes your Analysis needs (e.g., users, devices, entities). Read more about [Creating a Policy](/docs/tagoio/tagorun/access-management/creating-a-policy.md). + When you create an analysis, it does not have the necessary permissions to access data or run services. For that reason, you need to generate a policy that gives access only to operations and data within scopes your Analysis needs (e.g., users, devices, entities). Read more about [Creating a Policy](/docs/tagoio/tagorun/access-management/creating-a-policy.md). 3. **Code your script** Use the [SDK](/docs/tagoio/analysis/sdk/) for your runtime to read/write data, call external APIs, and log output. Keep functions idempotent when possible. diff --git a/docs/tagoio/analysis/running-analysis-as-external-using-deno.md b/docs/tagoio/analysis/running-analysis-as-external-using-deno.md index 67ca88f4..47fffc1c 100644 --- a/docs/tagoio/analysis/running-analysis-as-external-using-deno.md +++ b/docs/tagoio/analysis/running-analysis-as-external-using-deno.md @@ -15,7 +15,7 @@ Running an Analysis externally with Deno provides several advantages: Deno is a secure runtime for JavaScript and TypeScript built on V8, Rust, and Tokio. It includes TypeScript support out of the box, a built‑in formatter and linter, and secure defaults. Learn more about [Deno](https://deno.land). -Visit the Deno Installation Guide for platform‑specific instructions: https://deno.land/manual/getting_started/installation +Visit the [Deno Installation Guide](https://deno.land/manual/getting_started/installation) for platform‑specific instructions. ## 2. Create your Analysis @@ -84,6 +84,6 @@ You should see output indicating the Analysis is connected and waiting for trigg ## More Examples -Check our Deno Analysis examples: https://github.com/tago-io/analysis-snippets/tree/main/snippets +Check our [Deno Analysis examples](https://github.com/tago-io/analysis-snippets/tree/main/snippets). You now have everything needed to run external Analysis with Deno, leveraging TypeScript support, remote imports, and modern development tools to create powerful TagoIO applications. \ No newline at end of file diff --git a/docs/tagoio/analysis/running-analysis-as-external-using-nodejs.md b/docs/tagoio/analysis/running-analysis-as-external-using-nodejs.md index 72283bba..98a394d6 100644 --- a/docs/tagoio/analysis/running-analysis-as-external-using-nodejs.md +++ b/docs/tagoio/analysis/running-analysis-as-external-using-nodejs.md @@ -27,7 +27,7 @@ In order to start writing your code, you first must set up the environment with **2.2** If the folder is empty, run `npm init` and fill in all prompted requests. If this is your first time, you can leave all defaults by just pressing enter. -**2.3** Now install the Tago SDK and the TagoIO‑Builder SDK: +**2.3** Now install the TagoIO SDK and the TagoIO‑Builder SDK: ```bash npm install --save @tago-io/sdk @@ -55,9 +55,9 @@ In order to do that, every analysis has the following line below. Replace `MY-AN module.exports = new Analysis(myAnalysis, { token: '**MY-ANALYSIS-TOKEN-HERE**' } ); ``` -You can get the analysis token by accessing your analysis page at TagoIO and selecting **External** for “Run the scripts from”. Create a new analysis if you don’t have any. +You can get the analysis token by accessing your analysis page at TagoIO and selecting **External** for “Runs on”. Create a new analysis if you don’t have any. -![Image 2](/docs_imagem/tagoio/1600873613832-4Vc.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1769103706398.png) Now run the script from your command line: @@ -67,11 +67,11 @@ node ./analysis.js You should see a prompt similar to this: -![Image 3](/docs_imagem/tagoio/Screen-20Shot-202019-03-06-20at-2016.32.35-37A.png) +![Image 3](/docs_imagem/tagoio/rounded-image-1769103781795.png) -Go back to Tago and click **Save and Run** or just **Run** to run your script. You can also configure an action to run your script automatically. +Go back to TagoIO and click **Run** to run your script. You can also configure an [Action](/docs/tagoio/actions/running-analysis-via-action.md) to run your script automatically. -![Image 4](/docs_imagem/tagoio/1611084833441-Ers.png) +![Image 4](/docs_imagem/tagoio/rounded-image-1769103742011.png) ## 4. Use Analysis‑Builder to Upload the Script @@ -97,4 +97,4 @@ You can check our analysis examples with the full environment already set up for * [Average Min/Max Example](https://github.com/tago-io/analysis-example-avgMinMax) * [Find Example](https://github.com/tago-io/analysis-example-find) -Now you have everything you need to know about running analysis in your machine and can start to creating full applications and powerful analysis using TagoIO +Now you have everything you need to know about running analysis on your machine and can start creating full applications and powerful analysis using TagoIO. diff --git a/docs/tagoio/analysis/script-editor.md b/docs/tagoio/analysis/script-editor.md index f7642a75..6c3fb4df 100644 --- a/docs/tagoio/analysis/script-editor.md +++ b/docs/tagoio/analysis/script-editor.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- With the script editor, developers can create and edit their own scripts at TagoIO. These scripts are executed according to the configuration defined in the Analysis section. -To use the script editor, go to [Analysis](/docs/tagoio/analysis/), then create or edit an analysis. Set the name, interval, and choose to run it at TagoIO. +To use the script editor, go to [Analysis](/docs/tagoio/analysis/), then create or edit an analysis. Set the name, runtime version, and choose to run it at TagoIO. :::warning @@ -13,13 +13,28 @@ The editor tab is only shown when you choose to run the script at TagoIO. ::: -By clicking the Analysis tab, you can open the editor. From there you can: -- Load scripts from your computer -- Download scripts from the editor +By clicking on the Analysis, you can open the editor. Here are some of the options you can find: +- Upload scripts from your local machine +- Change the maximum runtime of the script - Choose from one of our snippet examples +- Directly edit the script, environment variables, and more... -![TagoIO Script Editor screenshot](/docs_imagem/tagoio/script-editor-2.png) +![TagoIO Script Editor screenshot](/docs_imagem/tagoio/rounded-image-1764605320147.png) When you save the script, it will be deployed on TagoIO servers. You can then click **Run** to execute it immediately and view the results in the console below. -To learn more about our examples, you can visit our [Script Examples](/docs/tagoio/analysis/script-examples.md) article, or access the [Analysis](https://admin.tago.io/analysis) click on the "+ Add Analysis" button in, the top right corner and select a code example. +To learn more about our examples, you can visit our [Script Examples](/docs/tagoio/analysis/script-examples.md) article, or access the [Analysis](https://admin.tago.io/analysis), click on the "+ Add Analysis" button in the top right corner, and select a code example. + +## TagoAI Assistant + +The TagoAI Assistant helps you write, debug, and generate code for your Analysis scripts. +You can open it by clicking the star-shaped TagoAI Assistant button in the top-right corner of the script editor. + +![TagoAI Assistant](/docs_imagem/tagoio/rounded-image-1769103890139.png) + +The assistant lets you: + +- Ask questions about your current script. +- Get help writing or improving code. +- Debug issues by asking about errors or unexpected behavior using the Analysis console. +- Generate script snippets tailored to your needs. diff --git a/docs/tagoio/analysis/script-examples.md b/docs/tagoio/analysis/script-examples.md index 1d299a24..2cdba47f 100644 --- a/docs/tagoio/analysis/script-examples.md +++ b/docs/tagoio/analysis/script-examples.md @@ -5,7 +5,9 @@ tags: ["tagoio"] --- TagoIO provides a list of script examples to help you learn how to use the Analysis service. These examples show how to get and insert data into a device's data storage, send emails, execute calculations, and perform other useful tasks that can be added to your applications. +![Script Examples](/docs_imagem/tagoio/rounded-image-1761142560772.png) + ## Accessing the examples -To access the examples, [create one Analysis](/docs/tagoio/analysis/creating-analysis.md) and go to the "Analysis" tab. There you will find the option to **Load a snippet**. +To access the examples, [create an Analysis](/docs/tagoio/analysis/creating-analysis.md) and go to the "Analysis" tab. There you will find the option to **Load a snippet**. -After selecting one example, the code will be added to the body of the script screen. +After selecting an example, the code will be added to the body of the script screen. diff --git a/docs/tagoio/analysis/sdk/nodejs-sdk.md b/docs/tagoio/analysis/sdk/nodejs-sdk.md index e794c61c..bed2d619 100644 --- a/docs/tagoio/analysis/sdk/nodejs-sdk.md +++ b/docs/tagoio/analysis/sdk/nodejs-sdk.md @@ -3,15 +3,10 @@ title: "Node.js SDK" description: "This article links to the TagoIO Node.js SDK documentation, points to the legacy SDK docs for version 9.x.x, and warns about API request rate limits." tags: ["tagoio"] --- -## Documentation -You can access the Node.js SDK documentation here: - -https://js.sdk.tago.io +You can access the Node.js SDK documentation [here](https://js.sdk.tago.io). ## Legacy (9.x.x) documentation -If you are looking for documentation for the old version (9.x.x), access it here: - -https://tago-sdk-js-documentation.rtfd.io/ +If you are looking for documentation for the old version (9.x.x), access it [here](https://tago-sdk-js-documentation.rtfd.io/). > Note: The old SDK will be discontinued in 2030. diff --git a/docs/tagoio/api/api_overview.md b/docs/tagoio/api/api_overview.md index 81963c34..47ac8bda 100644 --- a/docs/tagoio/api/api_overview.md +++ b/docs/tagoio/api/api_overview.md @@ -52,9 +52,9 @@ typically receive responses similar to the examples below: } ``` -- status: boolean indicating general request success (true) or failure (false). -- result: contains the response data (array or object) or error details. -- message: optional text included for warnings or additional information on +- **status**: boolean indicating general request success (true) or failure (false). +- **result**: contains the response data (array or object) or error details. +- **message**: optional text included for warnings or additional information on failures. For more details and endpoints, refer to the full @@ -87,7 +87,7 @@ can also be defined. Add them in the header of your HTTP request: | Authentication | Any Token (Account or Device) | Check the [usage policy](/docs/tagoio/profiles/services/usage-policy.md) based -on number of requests per a certain period. +on the number of requests per a certain period. ## Regional endpoints diff --git a/docs/tagoio/dashboards/blueprint-dashboard.md b/docs/tagoio/dashboards/blueprint-dashboard.md index 1b24f1f9..b410c75a 100644 --- a/docs/tagoio/dashboards/blueprint-dashboard.md +++ b/docs/tagoio/dashboards/blueprint-dashboard.md @@ -20,4 +20,4 @@ This means that you can distribute the same Dashboard to hundreds of different T [Blueprint Devices](/docs/tagoio/devices/blueprint-devices-entities.md) are dynamic devices that can be changed by the User while viewing the Dashboard. Changing these devices will reload the data for the Widgets that use them. -![Image 5](/docs_imagem/tagoio/1592330671692-dtA.png) +![Image 5](/docs_imagem/tagoio/rounded-image-1769102998326.png) diff --git a/docs/tagoio/dashboards/creating-dashboard-tabs.md b/docs/tagoio/dashboards/creating-dashboard-tabs.md index a9ef3582..0c0c089d 100644 --- a/docs/tagoio/dashboards/creating-dashboard-tabs.md +++ b/docs/tagoio/dashboards/creating-dashboard-tabs.md @@ -14,7 +14,7 @@ Notice that in the example above we have three tabs: the dashboard itself, the c ## Creating & Editing a Tab -To create a **tab** on your application, go to the dashboard you want to create it, click the edit button to enter in **edit mode**, and then click on the settings button. +To create a **tab** on your application, go to the dashboard you want to create it in, click the edit button to enter **edit mode**, and then click on the settings button. diff --git a/docs/tagoio/dashboards/data-output-for-dashboards.md b/docs/tagoio/dashboards/data-output-for-dashboards.md index c476d5bc..499426b9 100644 --- a/docs/tagoio/dashboards/data-output-for-dashboards.md +++ b/docs/tagoio/dashboards/data-output-for-dashboards.md @@ -27,8 +27,8 @@ Data consumed by dashboards will not be counted against the [Data Output Service When your account approaches the predefined limit, you will receive a notification suggesting an upgrade to your plan. This notification will be sent to your Admin panel and to your registered email address. Note that you cannot increase the dashboard data output limit yourself (this is different from the limit control available for the general Data Output Service). -Customers on the Scale plan can request an increase in this limit by contacting our [Sales Team](https://tago.io/contact-us-us) or opening a ticket through our Help Center. - ### Monitoring your limit -You can monitor the amount of your dashboard's data output that has been consumed by accessing the account menu in the top right corner of your Admin panel and selecting the '[Hard Limits](https://admin.tago.io/limits/hard)' option – search for the row "**Dashboard Output**". +You can monitor the amount of your dashboard's data output that has been consumed by accessing the profile menu in the top left corner of your Admin panel and selecting the '[Hard Limits](https://admin.tago.io/limits/hard)' option – search for the row "**Dashboard Output**". + + diff --git a/docs/tagoio/devices/adding-devices-with-connectors.md b/docs/tagoio/devices/adding-devices-with-connectors.md index 6939d9ce..2e3953b9 100644 --- a/docs/tagoio/devices/adding-devices-with-connectors.md +++ b/docs/tagoio/devices/adding-devices-with-connectors.md @@ -6,7 +6,7 @@ sidebar_position: 1 --- [Connectors](/docs/tagoio/devices/payload-parser/connector/connector-overview.md) -enable you to create a [device](/docs/tagoio/devices/) with built‑in behaviors +allow you to create a [device](/docs/tagoio/devices/) with built‑in behaviors that allow it to communicate with a network easily. When creating devices at TagoIO, there are different ways to allow them to send @@ -18,10 +18,10 @@ and receive data through connectors: 2. When using external services from providers (e.g., LoRaWAN, Sigfox, or cellular), it is necessary to generate an [Authorization](/docs/tagoio/integrations/general/authorization.md) per group - or application. + or application. The Authorization is used to direct data to the correct profile. That is why you need to select the right connector when creating your device at -TagoIO: to take advantage of the integrations already implemented with these +TagoIO: to take advantage of the integrations and parsers already implemented with these services. ## Connector functions diff --git a/docs/tagoio/devices/blueprint-devices-entities.md b/docs/tagoio/devices/blueprint-devices-entities.md index 12d1a045..c3fc4c23 100644 --- a/docs/tagoio/devices/blueprint-devices-entities.md +++ b/docs/tagoio/devices/blueprint-devices-entities.md @@ -19,14 +19,14 @@ Blueprint devices or entities are crucial for leveraging Blueprint Dashboards. T This feature is particularly beneficial when you want a single dashboard to be used by different end-users without exposing each other's data. It allows you to focus on one centralized dashboard, eliminating the need to maintain multiple dashboards for each type of end-user. -![Image 1](/docs_imagem/tagoio/external-82f6c83e.png) +![Image 1](/docs_imagem/tagoio/rounded-image-1767728631182.png) To create blueprint devices or entities, it is essential to first assign tags to them. For more information, please refer to the [Tags System documentation](/docs/tagoio/getting-started/tags-system.md). ### Creating a blueprint You can create blueprints during the creation of a blueprint dashboard or by accessing the Blueprint Settings on the edit page of your blueprint dashboard. -![Image 4](/docs_imagem/tagoio/external-e4b19db0.png) +![Image 4](/docs_imagem/tagoio/rounded-image-1767728352363.png) **Key concepts for each field:** @@ -40,6 +40,6 @@ You can add up to 20 blueprints in a single dashboard. ### Visualization Settings You can easily modify the appearance of your Blueprint and the behavior of the blueprint selector. -![Image 5](/docs_imagem/tagoio/external-c405fa26.png) +![Image 5](/docs_imagem/tagoio/rounded-image-1767728974371.png) For instructions on creating and configuring blueprints or adjusting visualization options, see [Creating a blueprint](/docs/tagoio/dashboards/blueprint-dashboard.md) and [Visualization Settings](/docs/tagoio/widgets/). diff --git a/docs/tagoio/devices/configuration-parameters-for-devices.md b/docs/tagoio/devices/configuration-parameters-for-devices.md index eaaba80f..9c19a493 100644 --- a/docs/tagoio/devices/configuration-parameters-for-devices.md +++ b/docs/tagoio/devices/configuration-parameters-for-devices.md @@ -5,20 +5,17 @@ tags: ["tagoio", "devices"] --- Configuration Parameters are key-value pairs that enable you to customize the behavior of your [Devices](/docs/tagoio/devices/) in different scenarios. For example, you can use them to specify how to decode data or send downlink messages, filter your devices on [Widgets](/docs/tagoio/widgets/), or interact with [API & Analysis](/docs/tagoio/analysis/) scripts. -Configuration Parameters are stored on the configuration page of your device. You can access them by clicking on the Devices module in the left menu and selecting a device. You will see a tab called "Configuration Parameters", where you can add, edit, or delete parameters. You can set parameters and retrieve them later by making a request from the device. +Configuration Parameters are stored on the configuration page of your device. You can access them by clicking on the Devices module in the left menu and selecting a device. You will see a tab called "Parameters", where you can add, edit, or delete parameters. You can set parameters and retrieve them later by making a request from the device. - +![Configuration Parameters](/docs_imagem/tagoio/rounded-image-1765393546195.png) ## How it works Each Configuration Parameter has three configurable fields: -1. **Key**: Name of the parameter that you can use to reference it in your code or widgets. - -2. **Value**: The value you want to assign to your device for that parameter. - -3. **Read & Unread**: A boolean value (true or false) that indicates whether the parameter has been sent to the device. - +1. **Read & Unread**: A boolean value (true or false) that indicates whether the parameter has been sent to the device. +2. **Key**: Name of the parameter that you can use to reference it in your code or widgets. +3. **Value**: The value you want to assign to your device for that parameter. :::note diff --git a/docs/tagoio/devices/data-management/chunk-management.md b/docs/tagoio/devices/data-management/chunk-management.md index 317f03b0..02797c03 100644 --- a/docs/tagoio/devices/data-management/chunk-management.md +++ b/docs/tagoio/devices/data-management/chunk-management.md @@ -7,9 +7,9 @@ The Chunk Management feature lets you view and manage the data of Immutable devi ## Accessing Chunk Management -Access the Device module and select a Device Data Optimized (Immutable) device type from your list. In the device view you will find the Chunk Management section, which displays a graph of your data chunks according to the period you chose when creating the device. See [Immutable devices](/docs/tagoio/devices/) and [Device](/docs/tagoio/devices/) for details on device types and the Device module. +Access the Device module and select a Device Data Optimized (Immutable Device) from your list. In the device page, you will find the Chunks section, which displays a graph of your data chunks according to the period you chose when creating the device. See [Immutable devices](/docs/tagoio/devices/) and [Device](/docs/tagoio/devices/) for details on device types and the Device module. - +![Data Export](/docs_imagem/tagoio/rounded-image-1765391012273.png) ## Export chunks to TagoIO Files diff --git a/docs/tagoio/devices/data-management/data-export.md b/docs/tagoio/devices/data-management/data-export.md index 86b86fba..6b3d28da 100644 --- a/docs/tagoio/devices/data-management/data-export.md +++ b/docs/tagoio/devices/data-management/data-export.md @@ -49,8 +49,6 @@ chunks. Learn more about exporting data chunks here: ::: - - Notes: - Use filtering options on the device "Data" tab to limit the exported data and diff --git a/docs/tagoio/devices/data-management/data-retention-feature.md b/docs/tagoio/devices/data-management/data-retention-feature.md index 5737fc9c..ff1d57f3 100644 --- a/docs/tagoio/devices/data-management/data-retention-feature.md +++ b/docs/tagoio/devices/data-management/data-retention-feature.md @@ -13,7 +13,7 @@ costs by deleting data that does not need to be kept long-term. :::info The Data Retention feature is available only for -[Optimized Device Data (Immutable)](/docs/tagoio/devices/). +[Optimized Device Data](/docs/tagoio/devices/). ::: @@ -21,20 +21,19 @@ The Data Retention feature is available only for To configure Data Retention, you must select two fields: -- **Period** — the chunk period for retaining data (for example, Daily or - Monthly). +- **Period** — the chunk period for retaining data. - **Retention** — how many of those periods to keep the data. These two fields are combined to create the device’s data retention policy. - +![Data Retention](/docs_imagem/tagoio/rounded-image-1765391484647.png) UI helper text shown in the configuration: -- This selection limits the storage for this device to 1 Million data registers - per month (you cannot change this Period). But you can always edit the - Retention from 0 to 36 months. -- The retention starts considering the current period — if you select “0” months +- This selection limits the storage for this device to 1 million data registers + per month, you cannot change the chunk period. But you can always edit the + retention from 0 to 36 months. +- The retention starts considering the current period — if you select 0 months it will delete all data when a new month starts. ## Period @@ -45,13 +44,17 @@ how long data should be kept on your device. Examples and important considerations: -- Setting Period to _Monthly_ allows storing up to 1 Million data registers per +- Setting Period to _Monthly_ allows storing up to 1 million data registers per month. -- Setting Period to _Daily_ allows storing up to 1 Million data registers per +- Setting Period to _Daily_ allows storing up to 1 million data registers per day. -- You cannot change the Period field later on, so choose it carefully. -- Retention can be edited between 0 and 36 months. Selecting 0 months will - delete all data when the next period starts. +- You cannot change the Chunk Period field later on, so choose it carefully. +- Chunk Retention can be edited between the range of the selected period. + +:::info + +Setting your devices Chunk Retention to 0 will cause the platform to delete all device data when the next period starts. +::: ### Retention ranges by period @@ -62,9 +65,12 @@ Examples and important considerations: | Monthly | 0–36 | | Quarterly | 0–36 | -Each period chunk is limited to **1 Million registers**.\ -The retention feature keeps data for the selected retention _plus_ the data in -the current period. +:::tip +Each period chunk is limited to **1 million registers**. The retention feature keeps data for the selected retention _plus_ the data in +the current period. + +Keep that in mind when setting your Chunk Retention, if your device sends more than 1 million data registers per period, you will lose data. +::: ### How it works diff --git a/docs/tagoio/devices/data-management/device-data-management.md b/docs/tagoio/devices/data-management/device-data-management.md index ca5f0b92..c7c2a5a2 100644 --- a/docs/tagoio/devices/data-management/device-data-management.md +++ b/docs/tagoio/devices/data-management/device-data-management.md @@ -6,25 +6,23 @@ sidebar_position: 1 --- The device page provides tools for visualizing, filtering, editing, importing, and exporting variables to facilitate management of the data received from your device. You can access these tools by navigating to the Device module, selecting a device, and clicking on the "Data" tab. Refer to the Device module documentation for navigation details. - - ## Amount of data records -The amount of data stored in each device is displayed at the top of the page. When the number of data records exceeds 1,000 registers, TagoIO will start to display a truncated value. This represents an estimated number of data records stored in the device. +The amount of data stored in each device is displayed at the right side of the page. When the number of data records exceeds 1,000 registers, TagoIO will start to display a truncated value. This represents an estimated number of data records stored in the device. When the value is greater than 1,000 registers it may be shown with a letter suffix: **K** for thousand, **M** for million, **B** for billion, and **T** for trillion. -![Image 2](/docs_imagem/tagoio/external-549c623a.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1767725721851.png) -![Image 3](/docs_imagem/tagoio/external-525092fc.png) +![Image 3](/docs_imagem/tagoio/rounded-image-1767726076769.png) ## Last Input The last input information refers to the last time the device received communication; it does not necessarily mean that the data sent was actually stored as data. This information is useful to verify the last time your sensor received an attempt of data input. -If you desire to verify if your data was received and added to your device, the best approach is to check the variable in the **Data** tab, or use the [Live Inspector](/docs/tagoio/devices/live-inspector.md) feature. +If you want to verify if your data was received and added to your device, the best approach is to check the variable in the **Data** tab, or use the [Live Inspector](/docs/tagoio/devices/live-inspector.md) feature. -![Image 5](/docs_imagem/tagoio/external-474cf6ac.png) +![Image 5](/docs_imagem/tagoio/rounded-image-1767726141891.png) ## Managing variable data @@ -34,9 +32,15 @@ The **Data** tab on your device page lists all stored variables, including their Filter options within the **Data** tab enable you to refine your variable search based on specific criteria. -The table visualization can be customized by adjusting column visibility or changing the time format; this option is accessible through the cog icon in the table's lower-left corner. +The table visualization can be customized by adjusting column visibility or changing the time format; this option is accessible through the display icon immediately above the table, on the left side. + +![Image 6](/docs_imagem/tagoio/rounded-image-1767727513332.png) + +:::tip + +You can also increase the number of rows that are displayed per page by clicking the display icon and selecting the desired number of rows. -![Image 6](/docs_imagem/tagoio/external-e4612149.png) +::: ## Editing and deleting variables individually @@ -44,7 +48,7 @@ For [mutable devices](/docs/tagoio/devices/), individual variables can be edited To delete variables, first select the ones you want to remove. Once selected, click **Delete selected** to proceed with the deletion. This action is irreversible. -![Image 7](/docs_imagem/tagoio/external-39e17ef8.png) +![Image 7](/docs_imagem/tagoio/rounded-image-1767727705660.png) For [immutable devices](/docs/tagoio/devices/), it is not possible to edit data individually; data can only be deleted through the data chunks. Read more about it here: [Chunk Management](/docs/tagoio/devices/data-management/chunk-management.md). @@ -54,7 +58,7 @@ To import data in bulk into your device, navigate to the **Data** tab and click The supported file format is CSV. -![Image 8](/docs_imagem/tagoio/external-e4940a38.png) +![Image 8](/docs_imagem/tagoio/rounded-image-1767727794882.png) The device payload parser does not execute during data import. Therefore, ensure that the data is properly formatted before importing. @@ -104,7 +108,7 @@ To back up your device data, click the **More** button located in the top right The tool automatically backs up all your device data. If you need to apply filters before backing up, use the Data Export function to refine your data, and then save it locally or in your Files. For [Immutable devices](/docs/tagoio/devices/), clicking the **Backup to Files** button will redirect you to the **Chunk Management** tab, where you can select specific chunks of data to back up to your Files. -![Image 11](/docs_imagem/tagoio/external-df29aa3f.png) +![Image 11](/docs_imagem/tagoio/rounded-image-1767727863200.png) ### File Address Template @@ -134,6 +138,6 @@ When exporting a chunk to a location where a file already exists, all the data w ## Emptying your Device Data -While it's feasible to remove variables one by one, there's a more efficient method to wipe all data simultaneously. +While it's possible to remove variables one by one, there's a more efficient method to wipe all data simultaneously. Navigate to the [Device](https://admin.tago.io/devices) module and choose the device you wish to clear. Then, click the **More** button located in the top right corner, then select **Empty Device Data** under the **Data** tab. diff --git a/docs/tagoio/devices/device-emulator/device-emulator-functions.md b/docs/tagoio/devices/device-emulator/device-emulator-functions.md index f9a2a6b3..bd51ad7f 100644 --- a/docs/tagoio/devices/device-emulator/device-emulator-functions.md +++ b/docs/tagoio/devices/device-emulator/device-emulator-functions.md @@ -14,8 +14,8 @@ JSON example using a function: [ { "variable": "temperature", - "unit": "F", - "value": $random$ + "value": $random$, + "unit": "F" } ] ``` @@ -29,16 +29,19 @@ temperature,$random$,2019-09-19,1568913302243 ## List of functions -- $random$: This function will be replaced by a random number that ranges from 0 to 100 whenever you send your payload. -- $randomBoolean$: This function will be replaced by a random boolean (true or false) whenever you send your payload. -- $busRoute$: This function will be replaced by a sequential bus route through Chicago. The location will change to a new one every time you send your payload. You should only use this function in the `location` field of a JSON payload. -- $sequential$: This function will be replaced by a number that is increased by 1 every time you send your payload. -- $sequentialHex$: This function will be replaced by a hexadecimal value that is increased by 1 every time you send your payload. If you are using this function in a JSON payload, wrap it around quotes (`"$sequentialHex$"`). -- $timestamp$: This function will be replaced by the current date and time as a Unix epoch timestamp. -- $date$: This function will be replaced by the current date in the format `YYYY-MM-DD`. If you are using this function in a JSON payload, wrap it around quotes (`"$date$"`). +- **$random$**: This function will be replaced by a random number that ranges from 0 to 100 whenever you send your payload. +- **$randomBoolean$**: This function will be replaced by a random boolean (true or false) whenever you send your payload. +- **$busRoute$**: This function will be replaced by a sequential bus route through Chicago. The location will change to a new one every time you send your payload. You should only use this function in the `location` field of a JSON payload. +- **$sequential$**: This function will be replaced by a number that is increased by 1 every time you send your payload. +- **$sequentialHex$**: This function will be replaced by a hexadecimal value that is increased by 1 every time you send your payload. If you are using this function in a JSON payload, wrap it around quotes (`"$sequentialHex$"`). +- **$unixtime$**: This function will be replaced by the current date and time as a Unix epoch timestamp. +- **$timestamp$**: This function will be replaced by the current date and time as 'YYYY-MM-DDTHH:mm:ss.sssZ' (ISO-8601) format. +- **$date$**: This function will be replaced by the current date in the format `YYYY-MM-DD`. If you are using this function in a JSON payload, wrap it around quotes (`"$date$"`). :::tip If you are unsure of how to use functions, look for samples in the editor. +![Device Emulator functions samples](/docs_imagem/tagoio/rounded-image-1766777720645.png) + ::: diff --git a/docs/tagoio/devices/device-emulator/device-emulator.md b/docs/tagoio/devices/device-emulator/device-emulator.md index f16314fb..a462c53b 100644 --- a/docs/tagoio/devices/device-emulator/device-emulator.md +++ b/docs/tagoio/devices/device-emulator/device-emulator.md @@ -11,7 +11,7 @@ validate and send your data package. To access the device emulator, go to the [Device](/docs/tagoio/devices/) section, select the device, and then click on the Emulator tab. -![Device Emulator interface showing the Emulator tab, JSON payload editor, and a Send payload button](/docs_imagem/tagoio/device-emulator-2.png) +![Device Emulator interface showing the Emulator tab, JSON payload editor, and a Send payload button](/docs_imagem/tagoio/rounded-image-1766775932693.png) ## Supported payload types @@ -39,7 +39,7 @@ To send a JSON payload from the emulator, you will need to: 2. Edit the fields of the payload; 3. Click on **Send button** to send the payload. -![Example payload editor](/docs_imagem/tagoio/Screen-20Shot-202021-06-24-20at-2016.46.47-0OI.png) +![Example payload editor](/docs_imagem/tagoio/image.png) ### Functions @@ -47,7 +47,7 @@ Functions are helper variables that you can add to your payload. Each function has a purpose. To add a function to your payload, click on **Add function** button and select a function. -![Function selection dialog](/docs_imagem/tagoio/1624564657419-ttY.png) +![Function selection dialog](/docs_imagem/tagoio/rounded-image-1766775773235.png) To learn more about using functions in the device emulator, read the article [Device Emulator Functions](/docs/tagoio/devices/device-emulator/device-emulator-functions.md). @@ -58,14 +58,15 @@ The timer helps to automatically send your payload at a fixed time interval. This is extremely useful if you wish to see the data coming in while you look at a dashboard, for example. -![Timer interface](/docs_imagem/tagoio/1624568411436-YYo.png) +![Timer interface](/docs_imagem/tagoio/rounded-image-1766775810232.png) -> If you close the **Emulator** tab, the system will stop sending payloads. You -> may want to use the -> [Simulator](/docs/tagoio/devices/simulator-data-stream.md) or create a script -> to keep sending all the time. -> Before sending any kind of payload, always make sure that the device is -> **Active**. +:::tip +If you close the **Emulator** tab, the system will stop sending payloads. You may want to use the [Simulator](/docs/tagoio/devices/simulator-data-stream.md) or create a script to keep sending all the time. +::: + +:::warning +Before sending any kind of payload, always make sure that the device is **Active**. +::: Learn more in our [community](https://community.tago.io/). diff --git a/docs/tagoio/devices/device-emulator/using-the-device-emulator.md b/docs/tagoio/devices/device-emulator/using-the-device-emulator.md deleted file mode 100644 index 061eb276..00000000 --- a/docs/tagoio/devices/device-emulator/using-the-device-emulator.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: "Using the Device Emulator" -description: "This article explains how to use the TagoIO Device Emulator to send test payloads to your applications, the supported payload formats, and how to convert non-JSON data using a Payload parser." -tags: ["tagoio", "devices"] -sidebar_position: 1 ---- -If you want a quick way to send data to your applications but don't have your hardware device available, or you simply need to send data to debug your applications, you can use the Device Emulator. - -To access the emulator, go to [Devices](/docs/tagoio/devices/), select the device, and then click on the Emulator tab. - -![Device Emulator interface showing the Emulator tab and payload editor](/docs_imagem/tagoio/using-the-device-emulator-2.png) - -## Supported payload formats - -You can send payloads in different formats, including: - -- Standard JSON (recommended) -- Raw payloads (for custom data structures, e.g., CSV) - -If you send raw data or any format other than JSON, you must create a [Payload parser](/docs/tagoio/devices/payload-parser/building-your-own-parser.md) to convert the output into the JSON format that TagoIO accepts. - -## Example JSON payload - -Below is a simple JSON example you can use in the Emulator payload editor: - -```json -{ - "variable": "temperature", - "value": 7 -} -``` - -## Sending the payload - -- Enter your payload in the Emulator editor. -- Press the Send payload button (▶) to send the payload. -- TagoIO's API response will appear in the right‑hand panel labeled “TagoIO’s API response”. If nothing has been sent yet, the panel will display: “Nothing sent yet. Press the ▶ button to send the payload.” - -## Notes and references - -- Access the emulator from: [Devices](/docs/tagoio/devices/) → select your device → Emulator tab. -- If you need to convert non‑JSON payloads, see the [Payload parser](/docs/tagoio/devices/payload-parser/building-your-own-parser.md) documentation for instructions on creating parsers that output JSON for TagoIO. -- You can also use Functions and Timer to send data automatically to your devices. diff --git a/docs/tagoio/devices/device-token.md b/docs/tagoio/devices/device-token.md index fde180c3..80520db2 100644 --- a/docs/tagoio/devices/device-token.md +++ b/docs/tagoio/devices/device-token.md @@ -14,12 +14,13 @@ The secret key used between TagoIO and your device is called a Device Token. Any ## Finding the Device Token -- Open the device in the TagoIO Console (see the Devices documentation for details). -- Go to the "General Information" tab for that device. -- Click the reveal button to show the token. -- You can copy the token by clicking the "Copy token" option. +- Open the [Devices](https://admin.tago.io/devices) module in the TagoIO Console. +- Select the device you want to get the token for. +- Go to the "General" tab. +- In the "Token & Serial Number" window, click on the 3 dot menu. +- Select "Copy Token" to copy the token to the clipboard. - +![Device Token](/docs_imagem/tagoio/rounded-image-1764604280634.png) ## Security recommendations diff --git a/docs/tagoio/devices/getting-data.md b/docs/tagoio/devices/getting-data.md index 9caef09e..d7a43a91 100644 --- a/docs/tagoio/devices/getting-data.md +++ b/docs/tagoio/devices/getting-data.md @@ -29,7 +29,7 @@ The following querystring parameters are supported: | Key | Type | Description | |-------------|-----------------|-------------| | variable | string or array | Get variables | -| query | string | Pre-defined by Tago | +| query | string | Pre-defined by TagoIO | | qty | string | Maximum number of data points to be returned | | start_date | string | Start date (e.g., "1 day" or ISO string) | | end_date | string | End date (e.g., "1 day" or ISO string) | diff --git a/docs/tagoio/devices/index.md b/docs/tagoio/devices/index.md index 72c2ca44..e7a673c4 100644 --- a/docs/tagoio/devices/index.md +++ b/docs/tagoio/devices/index.md @@ -4,10 +4,10 @@ description: "This article explains what a Device is in TagoIO, how devices comm tags: ["tagoio", "devices"] --- -Device is the link between your external things and the data in your account. To +Devices are the link between your external things and the data in your account. To allow anything to send or receive data from TagoIO, you need to create a device. The communication between external devices and TagoIO is done via HTTP or MQTT -using JSON format. To enable this communication, a device must be created within +using [JSON format](/docs/tagoio/devices/sending-data.md). To enable this communication, a device must be created within the platform; this involves specifying the device type and configuring it to send and receive data correctly. @@ -40,18 +40,17 @@ storage to be used. There are two types of data storage you can choose from: ### Device Optimized Data (Immutable database) - Stores up to **36 million** data points per device. +- Native [data retention](/docs/tagoio/devices/data-management/data-retention-feature.md). - Highly optimized for short and long retention periods; query responses are faster, which means less latency for the devices and a cost reduction when running an [Analysis](/docs/tagoio/analysis/creating-analysis.md). - Because the data is immutable, no one can change or delete individual sets of data – ideal for compliance. -- Data stored in the optimized device can only be removed by the - [data retention policy](/docs/tagoio/devices/data-management/data-retention-feature.md). ### Managed Data Optimized (Mutable database) - Allows you to edit or delete data. -- **No** data retention. +- **No** native data retention; you can utilize Analysis to delete data on a scheduled basis. - Limited to **50 k** data registers. - Optimized for the storage and manipulation of configurable variables coming from sensors, web services, and forms. @@ -95,8 +94,8 @@ storage to be used. There are two types of data storage you can choose from: ## Emulating data sending -Inside your device’s page, find the **Emulator** tab where you can send data to -your device as if it was sent by a real sensor. +Inside your device's page, find the **Emulator** tab where you can send data to +your device as if it were sent by a real sensor. ## Customizing behavior of your device diff --git a/docs/tagoio/devices/live-inspector.md b/docs/tagoio/devices/live-inspector.md index 59cd44a5..e2badeba 100644 --- a/docs/tagoio/devices/live-inspector.md +++ b/docs/tagoio/devices/live-inspector.md @@ -1,36 +1,35 @@ --- title: "Live Inspector" -description: "The Live Inspector is a developer tool in TagoIO used to debug parser scripts and monitor device traffic; this article explains how to open and use the Live Inspector from a device page." +description: "Use the Live Inspector to debug parser scripts and monitor device traffic in real time." tags: ["tagoio"] --- -The live inspector is a tool for developers to debug -[parser scripts](/docs/tagoio/devices/payload-parser/index.md) and monitor traffic to -and from [devices](/docs/tagoio/devices/). +The Live Inspector helps you debug [parser scripts](/docs/tagoio/devices/payload-parser/index.md) and watch all the traffic going to and from your [devices](/docs/tagoio/devices/). It is a real-time monitoring tool that shows you exactly what data is flowing between TagoIO and your device. -To access the live inspector, go to the [Device](https://admin.tago.io/devices), -select the device, and click the Live Inspector tab. +Open a device from the [Device page](https://admin.tago.io/devices), then click the **Live Inspector** tab and start viewing data by clicking on the **Inspect** button. -![Device page showing the Live Inspector tab highlighted](/docs_imagem/tagoio/live-inspector-2.png) +![Device page showing the Live Inspector tab highlighted](/docs_imagem/tagoio/rounded-image-1766777978480.png) -Start the live inspector by clicking the green arrow on the right of the Live -Inspector panel. +:::tip +When inspecting is activated and new data arrives, the Inspector tab will be briefly highlighted in yellow so you don’t miss incoming activity in case you are in a different tab on the device page. +::: -![Live Inspector panel with search, page-size controls, and green start arrow](/docs_imagem/tagoio/live-inspector-2.png) +## How it works -## Live Inspector overview +The Live Inspector shows all active connections for the device. It only runs while you're on the Live Inspector page. + +The interface includes: + +- **Search field** - Filter messages as they come in +- **Max Connections** - Choose how many items to show (25, 50, 100, or 500) +- **Download button** - Download the data as a CSV file +- **Clear button** - Clear the data from the Message Log +- **Start/stop button** - The green arrow toggles monitoring on and off +- **Message log** - Lists all incoming traffic and connection details + +Everything sent to or from the device appears in real time. Each message is logged and shown in the list. + +:::info +The inspector no longer stops when you navigate away, it keeps running in the background. It will stop when you close the browser tab or refresh the page. +::: -- With Live Inspector, you can view all active connections for the selected - device with TagoIO. -- The inspector is only visible while you are visiting the device's Live - Inspector page. -- Typical UI elements in the Live Inspector: - - A search field to filter incoming messages. - - Page-size controls (e.g., 25, 50, 100, 500) to adjust how many items are - shown per page. - - A green start/stop arrow to begin or pause live monitoring. - - Log/list area showing incoming device traffic and connection details. -- All traffic to and from the device is monitored in real time; each package - sent is recorded and displayed in the Live Inspector. -- The inspector stops automatically when you leave the page or close the - browser; it does not run in the background after the window has been closed. diff --git a/docs/tagoio/devices/payload-parser/connector/connector-overview.md b/docs/tagoio/devices/payload-parser/connector/connector-overview.md index deb0acd0..d97b83fd 100644 --- a/docs/tagoio/devices/payload-parser/connector/connector-overview.md +++ b/docs/tagoio/devices/payload-parser/connector/connector-overview.md @@ -21,8 +21,8 @@ data. ## Creating a connector To create a new connector, go to the -[Connector management page](https://admin.tago.io/integrations/connector) and -press the '+ Add connector' on the right side of the page:' +[Integrations](https://admin.tago.io/integrations/connector) page and +press the '+ Add connector' on the right side of the page. You must specify the connector's name and the network(s) it belongs to. You can add as many networks as you like, but at least one network must be selected. diff --git a/docs/tagoio/devices/payload-parser/connector/sharing-connectors-networks.md b/docs/tagoio/devices/payload-parser/connector/sharing-connectors-networks.md index 70157885..e203dd76 100644 --- a/docs/tagoio/devices/payload-parser/connector/sharing-connectors-networks.md +++ b/docs/tagoio/devices/payload-parser/connector/sharing-connectors-networks.md @@ -14,27 +14,22 @@ To share a custom Connector or Network with another Profile: 1. Go to the [Integrations page](https://admin.tago.io/integrations/connector). 2. Select the connector or network you want to share. 3. Open the Share tab. +3. Click on the "Invite to Connector" or "Invite to Network" button. 4. Enter the Profile ID of the person you want to share it with. 5. Click the Share button. Note: Profiles with access to the shared connector cannot modify it; they can only use it to create devices. - + ![Share Connector](/docs_imagem/tagoio/rounded-image-1764772930690.png) -The Share modal contains: -- Title: "Share connector" -- Input: "Profile ID" (field to enter the Profile ID to share this connector) -- Small note: "Profiles with access to the shared connector cannot modify it, only use it to create devices." -- Buttons: "Cancel" and "Share" +### Utilizing a shared Connector -### Utilizing the shared Connector +Once shared, the recipient profiles can select your connector when adding new devices through the [Connector Selection](https://admin.tago.io/integrations/connector) page. They can view all connectors that have been shared with them by navigating to the **My Shared Connectors** list. -Once shared, the recipient profiles can select your connector when adding new devices through the [Connector Selection](https://admin.tago.io/integrations/connector) page. They can view all connectors that have been shared with them by navigating to the **Shared Connectors** list. +### Utilizing a shared Network -### Utilizing the shared Network - -Custom networks are only applicable for Connectors created by you. To make your custom network available for your connector, head to the configuration page of your network within the [Integrations](https://admin.tago.io/integrations/connector) page. Then: -- Navigate to the **General Information** tab. +Custom networks are only applicable for Connectors created by you. To make your custom network available for your connector, head to the configuration page of your network within the [Integrations](https://admin.tago.io/integrations/connector) page and select the connector. Then: +- Navigate to the **General** tab. - Select your custom network from the "**Select the networks for this connector**" option. Ensure that the Profiles you are sharing the Connector with have access to at least one of the Networks used by the Connector. If the Connector is utilizing a non-public Network, it is crucial to share both the Connector and the Network with the Profile. diff --git a/docs/tagoio/devices/payload-parser/filtering-out-variables-with-parser-code.md b/docs/tagoio/devices/payload-parser/filtering-out-variables-with-parser-code.md index 33504a34..bdc55b48 100644 --- a/docs/tagoio/devices/payload-parser/filtering-out-variables-with-parser-code.md +++ b/docs/tagoio/devices/payload-parser/filtering-out-variables-with-parser-code.md @@ -23,7 +23,7 @@ For example, if your device sends data from TTN (The Things Network), most varia A variable called **location** is automatically created by combining the fields `latitude` and `longitude`. Use this combined field when plotting maps. -![Application Data Console screenshot](/docs_imagem/tagoio/filtering-out-variables-with-parser-code-2.png) +![Application Data Console screenshot](/docs_imagem/tagoio/rounded-image-1767729055179.png) ## Editing the parser - Go to [Devices](https://admin.tago.io/devices) at your Admin panel, select your device, open the device settings and go to the "Payload Parser" tab. diff --git a/docs/tagoio/devices/payload-parser/index.md b/docs/tagoio/devices/payload-parser/index.md index 41586b03..73aa8fa5 100644 --- a/docs/tagoio/devices/payload-parser/index.md +++ b/docs/tagoio/devices/payload-parser/index.md @@ -39,7 +39,7 @@ with that device. ## Parser settings -![Parser settings to enable the parsers](/docs_imagem/tagoio/payload-parser-2.png) +![Parser settings to enable the parsers](/docs_imagem/tagoio/rounded-image-1767033964525.png) > The script contained inside the parser from the Connector is not visible. @@ -64,7 +64,12 @@ For this example, let's connect a toaster to Tago. A toaster could send data to TagoIO when your bread is toasted in the following format: -![Image 4](/docs_imagem/tagoio/1544036821426-yHM.png) +```javascript +{ + "variable": "toastValues", + "value": "01 350 00" +} +``` The value above could represent XX YYY ZZ. Where: @@ -81,12 +86,31 @@ need to parse this payload. Let's code the Payload Parser to transform that payload into real variables. First, click on your Device and go to the Payload Parser tab. -![Image 5](/docs_imagem/tagoio/Screen-20Shot-202018-12-05-20at-2016.29.43-WbU.png) +![Image 5](/docs_imagem/tagoio/rounded-image-1767034014646.png) On the Payload Parser tab you will see the code editor. Then, you can write the following code: -![Image 6](/docs_imagem/tagoio/1544035425383-V2U.png) +```javascript +const rawValues = payload.find(item => item.variable === 'toastValues'); + +if (rawValues) { + const valuesString = rawValues.value; + + const splitValues = valuesString.split(' '); + + const successCode = splitValues[0]; + const tempF = splitValues[1]; + const errorCode = splitValues[2]; + + payload.push({ "variable": "successCode", "value": successCode }); + payload.push({ "variable": "temperature", "value": tempF, "unit": "F" }); + + if (errorCode !== '00') { + payload.push({ "variable": "error", "value": errorCode }); + } +} +``` Save, and you are ready. Now, every time the toaster sends those variables, the parser will transform it into real variables, and you can use them to build diff --git a/docs/tagoio/devices/payload-parser/metadata.md b/docs/tagoio/devices/payload-parser/metadata.md index 7a8e549a..d3bc5535 100644 --- a/docs/tagoio/devices/payload-parser/metadata.md +++ b/docs/tagoio/devices/payload-parser/metadata.md @@ -47,7 +47,7 @@ For example, this article uses the `color` and `icon` metadata fields in the fol You can use your own icon by placing the SVG file URL in the `icon` metadata field. For your SVG to be displayed correctly, make sure that it has the property **viewBox** before using it. -![Image 1](/docs_imagem/tagoio/iconMetadata-y6I.gif) +![Image 1](/docs_imagem/tagoio/peek_37.gif) ## Available Metadata Fields diff --git a/docs/tagoio/devices/payload-parser/payload-parser-troubleshooting.md b/docs/tagoio/devices/payload-parser/payload-parser-troubleshooting.md index 996dd464..f1bcf0ca 100644 --- a/docs/tagoio/devices/payload-parser/payload-parser-troubleshooting.md +++ b/docs/tagoio/devices/payload-parser/payload-parser-troubleshooting.md @@ -3,19 +3,19 @@ title: "Payload Parser Troubleshooting" description: "This article explains common problems that stop the Payload Parser from decoding device data on TagoIO and provides straightforward fixes for each issue." tags: ["tagoio"] --- -When using the Payload Parser on TagoIO, you may encounter common problems that stop the parser from decoding your device data correctly. When the parser stops, the data will not be saved on TagoIO. These problems are usually related to mistakes in how the payload parser code is written, but they can be fixed easily. +When using the Payload Parser on TagoIO, you may encounter common problems that prevent the parser from decoding your device data correctly. When the parser stops, the data will not be saved to TagoIO. These problems are usually related to mistakes in how the payload parser code is written, but they can be easily fixed. -For updates on system status, visit the health status page at https://status.tago.io/. +For updates on system status, visit the health [status page](https://status.tago.io/). ## Common Issues ### 1. Function Parse Error: Payload Parser Terminated Unexpectedly -This happens when the Payload Parser encounters an error in code that is not formatted correctly and stops working. For example, using a plain string as an error like: +This happens when the Payload Parser encounters an error in code that is not formatted correctly and stops working. For example, using a plain string as an error, like: - throw "my error message" can cause the parser to stop unexpectedly. -Fix: +**Fix:** - Use the proper JavaScript `Error` class when throwing errors. The Payload Parser uses JavaScript, so create errors like this: ```javascript @@ -30,8 +30,8 @@ This error appears when the Payload Parser tries to use a variable that hasn’t without first defining what `temp` is will produce a "not defined" error. -Fix: -- Always declare your variables before use with `const`, `let`, or `var`. This prevents the "not defined" error and avoids creating accidental global variables. +**Fix:** +- Always declare your variables before using them with `const`, `let`, or `var`. This prevents the "not defined" error and avoids creating accidental global variables. Examples of variable declaration: diff --git a/docs/tagoio/devices/simulator-data-stream.md b/docs/tagoio/devices/simulator-data-stream.md index 5bae16f7..79ea43c9 100644 --- a/docs/tagoio/devices/simulator-data-stream.md +++ b/docs/tagoio/devices/simulator-data-stream.md @@ -1,33 +1,26 @@ --- -title: "Simulator (Data Stream)" -description: "This article explains how to use TagoIO's Device Simulator (Simulator network) to feed real-time data into the platform when you don't have a physical sensor, and describes how simulated or real streams are delivered to device storage." +title: "Device Simulators" +description: "This article explains how to use TagoIO's Device Simulators to feed real-time data into the platform when you don't have a physical sensor, and describes how simulated or real streams are delivered to device storage." tags: ["tagoio"] --- -If you don't have a real sensor (hardware) to send data through the Internet, you can still try all of TagoIO's features by selecting device simulators that feed data in real time. It's like adding a virtual device. +If you don't have real sensor hardware to send data through the Internet, you can still try all of TagoIO's features by selecting device simulators that feed data in real time. It's like adding a virtual device. -![TagoIO Device Simulator interface showing connector selection and simulator options](/docs_imagem/tagoio/simulator-data-stream-3.png) +![TagoIO Device Simulator interface showing connector selection and simulator options](/docs_imagem/tagoio/rounded-image-1765392749974.png) TagoIO's server provides a continuous stream of data—whether that data is simulated (e.g., bus, truck, freezer) or real (e.g., weather conditions in Raleigh, NC)—through the Simulator network. Data is sent to the device's storage in TagoIO. ## Adding a Simulator Device -To use this feature, go to **[Devices](https://admin.tago.io/devices)**, then click on “+Add Device”, select the Network: **Simulator**, and from the list of connectors pick the one that simulates a type of device you want. For example, choose the “Bus Simulator” which will send location, fuel level, speed and other variables to your device data storage every 3 minutes. +To use this feature, go to **[Devices](https://admin.tago.io/devices)**, then click on “+ Add Device”, select the Network: **Simulator**, and from the list of connectors pick the one that simulates a type of device you want. For example, choose the “Bus Simulator” which will send location, fuel level, speed and other variables to your device data storage every 3 minutes. -After adding the device, a pop‑up will ask if you want to add a [dashboard](/docs/tagoio/dashboards/). Use this option to get a dashboard to start and edit from there. +After adding the device, a pop‑up will ask if you want to add a [dashboard](/docs/tagoio/dashboards/) from our [Dashboard Templates](/docs/tagoio/dashboards/distributing-dashboards.md). Use this option to get a dashboard to start and edit from there. - +:::tip -## Working with Dashboards, Actions, Scripts, and RUN +TagoIO provides a list of Dashboard Templates for [you to choose from](https://tago.io/dashboard-templates). Some of them are made specifically for simulators, so you can start with a dashboard that is already configured to your device! -From there you can create and edit: - -- [Dashboards](/docs/tagoio/dashboards/) -- [Actions](/docs/tagoio/actions/) -- [Scripts](/docs/tagoio/analysis/) -- [RUN](/docs/tagoio/tagorun) - -This is an easy and quick way to start with TagoIO! +::: ## Data Visibility and Live Inspector diff --git a/docs/tagoio/files/index.md b/docs/tagoio/files/index.md index 63ed0bb6..f43b2218 100644 --- a/docs/tagoio/files/index.md +++ b/docs/tagoio/files/index.md @@ -9,7 +9,7 @@ You and your IoT devices can send and receive files such as images, CSV, TXT, an File storage is commonly used to send and receive files from devices, store data that is generated by your devices, store images to be displayed in widgets, attach files to emails, or support any other needs you might have for storing files and controlling private or public access to them. -![Files interface example showing file list and metadata](/docs_imagem/tagoio/files-3.png) +![Files interface example showing file list and metadata](/docs_imagem/tagoio/rounded-image-1762432112336.png) To use the files via **Admin**, go to *Files* in the left menu. From there you can see and manage all the files and folders that are stored on your account, as well as upload new files. @@ -20,5 +20,6 @@ To use the files via **Admin**, go to *Files* in the left menu. From there you c - Drag‑and‑drop files onto the page to upload them to the current folder. - Select multiple files by holding **Shift** or **Ctrl** while clicking on the desired files. - Right‑click a file to open a context menu with actions such as rename, delete, move, and download. - ![Context menu example](/docs_imagem/tagoio/1627914062208-mNE.png) -- Selecting a row shows detailed information about the file or folder in the right‑side panel. + + ![Context menu example](/docs_imagem/tagoio/rounded-image-1765199766266.png) +- Selecting a row shows detailed information about the file or folder in the right‑side panel. \ No newline at end of file diff --git a/docs/tagoio/files/uploading-files.md b/docs/tagoio/files/uploading-files.md index c258a3f5..97dd0176 100644 --- a/docs/tagoio/files/uploading-files.md +++ b/docs/tagoio/files/uploading-files.md @@ -3,7 +3,7 @@ title: "Uploading Files" description: "This article explains how to upload files using the TagoIO admin platform, the default access setting for uploaded files, and a reminder about file visibility when using widgets." tags: ["tagoio"] --- -To upload a file using the admin platform, go to [Files](https://admin.tago.io/files) and click the `Upload File` button in the top-right corner of the page. +To upload a file using the admin platform, go to [Files](https://admin.tago.io/files) and click the "Upload File" button in the top-right corner of the page. @@ -19,7 +19,7 @@ Remember to always set your files to Public if you plan on using them inside wid If you do not wish to manually select the files, you can drag-and-drop them into a specific folder or into the main panel. -![Files list example](/docs_imagem/tagoio/files-2.gif) +![Files list example](/docs_imagem/tagoio/filesvid.gif) ## Folders diff --git a/docs/tagoio/getting-started/entities.md b/docs/tagoio/getting-started/entities.md index d8abe4ed..35e70d38 100644 --- a/docs/tagoio/getting-started/entities.md +++ b/docs/tagoio/getting-started/entities.md @@ -9,6 +9,8 @@ Within an Entity, you can create custom fields similar to columns in a tradition Once your information is stored, you can access the data through [Analysis](/docs/tagoio/analysis/), the [TagoIO API](https://api.docs.tago.io/), and—soon—[Widgets](/docs/tagoio/widgets/). +![Entity module](/docs_imagem/tagoio/rounded-image-1765546206780.png) + ## Creating an Entity To create a new Entity, open the [Entity module](https://admin.tago.io/entities) on your Admin page and click on "+ New Entity" (or the equivalent action). You will be prompted to define a name and add fields. Note that once an entity is created, its name cannot be changed; however, you can still add or remove fields as needed. diff --git a/docs/tagoio/getting-started/getting-started.md b/docs/tagoio/getting-started/getting-started.md index 36f81d44..a9e1e57e 100644 --- a/docs/tagoio/getting-started/getting-started.md +++ b/docs/tagoio/getting-started/getting-started.md @@ -32,14 +32,14 @@ your account. 4. In the field _"Device Name"_, add any name for your device. 5. Click the **Create Device** button. -![Image 1](/docs_imagem/tagoio/throw-miA.gif) +![Image 1](/docs_imagem/tagoio/creatingDevice.gif) All devices should use a valid [device-token](/docs/tagoio/devices/device-token.md) when accessing TagoIO. One device‑token is generated when a device is created and it is available for you to copy if you want to insert it in a real device. -![Image 2](/docs_imagem/tagoio/token-cj4.gif) +![Image 2](/docs_imagem/tagoio/deviceCreation2.gif) ### Step 2. Build a dashboard @@ -57,7 +57,7 @@ interact with your devices and share with others. You can build it with the be sent by the device as temperature, and click **Save** – your widget will be ready! -![Image 3](/docs_imagem/tagoio/temp-3UQ.gif) +![Image 3](/docs_imagem/tagoio/widgetcreation.gif) ### Step 3. Send data @@ -73,18 +73,26 @@ the OS that you are using. #### Mac or Linux Command Line Let’s use curl to post the data. Enter the following command replacing the -**YOUR_DEVICE_TOKEN** by the token created earlier for your device. +**<Device-Token>** by the token created earlier for your device. ```bash -curl -H "Content-Type: application/json" \ - -H "Device-Token: YOUR_DEVICE_TOKEN" \ - -X POST -d '{"variable":"temperature","value":100,"unit":"F"}' https://api.tago.io/data +curl -L 'https://api.us-e1.tago.io/data' \ +-H 'Content-Type: application/json' \ +-H 'Accept: application/json' \ +-H 'Device-Token: ' \ +-d '[ + { + "variable": "temperature", + "value": 27, + "unit": "F" + } + ]' ``` Try to send more data by changing the value of the ‘temperature’. Keep an eye on your dashboard. You should see something like this: -![Image 4](/docs_imagem/tagoio/1621971979910-jRM.png) +![Image 4](/docs_imagem/tagoio/rounded-image-1768488678984.png) #### Windows @@ -93,20 +101,18 @@ To send data, there are some tools that support HTTP communication like input as used above, you can make a POST by entering the URL, Device-Token, and configuration in Postman like this: -![Image 5](/docs_imagem/tagoio/postman1-OU0.png) +![Image 5](/docs_imagem/tagoio/rounded-image-1768488814377.png) Then, input the variable information in the JSON body. Make sure that you select the same configuration as shown in the picture below. -![Image 6](/docs_imagem/tagoio/postman2-rSE.png) +![Image 6](/docs_imagem/tagoio/rounded-image-1769086495362.png) The response should look like this: -![Image 7](/docs_imagem/tagoio/postman3-wEs.png) +![Image 7](/docs_imagem/tagoio/rounded-image-1769086543434.png) -![Image 8](/docs_imagem/tagoio/postman-DU8.gif) - -![Image 9](/docs_imagem/tagoio/1621972232616-8Gk.png) +![Image 8](/docs_imagem/tagoio/peek_36.gif) ### Step 4. Create complete solutions diff --git a/docs/tagoio/getting-started/notification.md b/docs/tagoio/getting-started/notification.md index ac06c579..87ee16e2 100644 --- a/docs/tagoio/getting-started/notification.md +++ b/docs/tagoio/getting-started/notification.md @@ -19,7 +19,7 @@ There are four types of notifications: Displayed when another user shares something with you. Example: "John wishes to share a Dashboard with you." -- Tago system\ +- TagoIO system\ Used by the TagoIO backend to notify users about the system or your account. Example: "There is a new application in the Healthcare industry that you may be interested in." @@ -33,12 +33,9 @@ There are four types of notifications: ## Viewing notifications When you log in to your account, you can see all your notifications in the -top‑right corner of the admin page. +bottom-left corner of the admin page with a blinking blue dot indicating unread notifications. -> The number in red indicates how many new notifications you have. If you have -> more than 99 notifications, it will display as "99+". - -![Notifications UI showing unread count](/docs_imagem/tagoio/notification-2.png) +![Notifications UI showing unread count](/docs_imagem/tagoio/rounded-image-1765546342632.png) ## Filtering and searching @@ -55,12 +52,10 @@ accept dashboards or profiles. In these cases, you need to first accept the request before the shared item is available to you. > The user who sent the request can track the status of the request by checking -> into the “Share” tab of each item (Dashboard/Profile). +> the “Share” tab of each item (Dashboard/Profile). -After you make a decision and choose to accept or decline a notification, the -system will change it to a faded‑like color and remove the blue unread icon. -TagoIO automatically removes all ignored notifications that are older than two -weeks. +After you accept or decline a notification, the system removes the dark blue unread icon. +TagoIO automatically removes all ignored notifications that are older than two weeks. ### Notifications from Applications diff --git a/docs/tagoio/getting-started/secrets.md b/docs/tagoio/getting-started/secrets.md index 5ae4de77..d93e3b24 100644 --- a/docs/tagoio/getting-started/secrets.md +++ b/docs/tagoio/getting-started/secrets.md @@ -5,13 +5,13 @@ tags: ["tagoio"] --- Secrets are encrypted environment variables used to store sensitive information such as passwords and API keys. Each secret consists of a key (the secret's name) and a value (the sensitive data). Secrets keep their contents hidden once encrypted, making them safer than regular environment variables for confidential data. -Unlike regular [Environment Variables](/docs/tagoio/analysis/environment-variables.md), secrets are encrypted so their contents remain hidden after encryption. This security feature is essential for protecting sensitive data within TagoIO. Secrets are especially useful when scripts or services need access to confidential information without exposing it to users or developers. You can retrieve secrets from the Analysis context in your [Analysis documentation](/docs/tagoio/analysis/) code and use them in some [Actions documentation](/docs/tagoio/actions/). +Unlike regular [Environment Variables](/docs/tagoio/analysis/environment-variables.md), secrets are encrypted so their contents remain hidden after encryption. This security feature is essential for protecting sensitive data within TagoIO. Secrets are especially useful when scripts or services need access to confidential information without exposing it to users or developers. You can retrieve secrets from the Analysis context in your [Analysis](/docs/tagoio/analysis/) code and use them in some [Actions](/docs/tagoio/actions/). -To start using secrets, open your [Admin](https://admin.tago.io/) panel , navigate to the Account menu, and select "Secrets". +To start using secrets, open your [Admin](https://admin.tago.io/) panel, and click on the "Secrets" button in the sidebar menu. Don't forget that you must [grant access to the Secrets to the Analysis](/docs/tagoio/getting-started/secrets#granting-your-analysis-access-to-secrets) you want to use them in. ## Creating a Secret -To create a secret, open the "Secrets" page in the Admin panel and click on "+ New Secret". For every secret you create, you must define: +To create a secret, open the "Secrets" page in the Admin panel and click on "+ New Secret". For every secret you create, you can define: - **Key** — the name used to reference the secret. *Keys cannot be edited once the secret is created, so choose your keys carefully.* diff --git a/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration.md b/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration.md index f4f9022d..9d44268d 100644 --- a/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration.md +++ b/docs/tagoio/getting-started/tagoio-mcp-ai-powered-iot-data-integration.md @@ -5,12 +5,12 @@ tags: ["tagoio", "integration"] --- The TagoIO MCP Server bridges AI‑powered development tools with your TagoIO IoT platform, enabling intelligent workflows that understand and interact with your real device data, configurations, and platform resources. -![TagoIO MCP in Claude AI](/docs_imagem/tagoio/claude_chat_mcp.png) +![TagoIO MCP in Claude AI](/docs_imagem/tagoio/rounded-image-1765546532507.png) ## What is a Model Context Protocol (MCP)? Model Context Protocol (MCP) is an open standard that connects AI assistants to external data sources and tools. When integrated with TagoIO, it allows AI models in your development environment to directly access your IoT data, analyze patterns, generate code, and provide context‑aware assistance based on your actual platform configuration. -![TagoIO MCP Diagram](/docs_imagem/tagoio/mcp_diagram.png) +![TagoIO MCP Diagram](/docs_imagem/tagoio/rounded-image-1765546565836.png) ## Core capabilities @@ -77,7 +77,7 @@ Track platform access and new user activity: #### Trend Analysis Perform complex queries across multiple data sources: -> Quote"Compare energy consumption patterns between weekdays and weekends for all smart meters" +> "Compare energy consumption patterns between weekdays and weekends for all smart meters" #### Anomaly Detection Identify unusual patterns in sensor data: diff --git a/docs/tagoio/getting-started/tags-system.md b/docs/tagoio/getting-started/tags-system.md index 21840460..52faf97c 100644 --- a/docs/tagoio/getting-started/tags-system.md +++ b/docs/tagoio/getting-started/tags-system.md @@ -43,7 +43,7 @@ When this tag is present on a resource, any attempt to delete it will be blocked Tags can be managed from several sources: 1. **TagoIO Interface** – Manually add or edit tags by clicking the asset and then selecting the Tags tab. -2. **Analysis SDK** – Programmatically add or edit tags from an analysis script using methods such as `account.devices.edit()` or `account.actions.edit()`. +2. **Analysis SDK** – Programmatically add or edit tags from an analysis script using methods such as `Resources.devices.edit()` or `Resources.actions.edit()`. 3. **TagoIO API** – Use REST API endpoints for each asset type to add or edit tags by sending HTTP requests with JSON payloads containing the tag information. ### Common use cases diff --git a/docs/tagoio/integrations/general/authorization.md b/docs/tagoio/integrations/general/authorization.md index fd1ce3f0..2c86b294 100644 --- a/docs/tagoio/integrations/general/authorization.md +++ b/docs/tagoio/integrations/general/authorization.md @@ -13,7 +13,7 @@ easier to scale your applications. :::info -Authorization is different from +A Authorization token is different than a [device-token](/docs/tagoio/devices/device-token.md). > When to use each: @@ -31,11 +31,13 @@ devices, follow these steps: 1. Go to the Device section of your TagoIO account and click the "[Authorization](https://admin.tago.io/devices/authorization)" button. - ![Devices list with Authorization button highlighted](/docs_imagem/tagoio/authorization-2.png) + + ![Devices list with Authorization button highlighted](/docs_imagem/tagoio/rounded-image-1769101086998.png) 2. In the next screen, enter a name you can identify later, fill any additional parameters requested by the integration, and press the Generate button. - ![Generate Authorization screen showing name and parameters fields](/docs_imagem/tagoio/authorization-3.png) + + ![Generate Authorization screen showing name and parameters fields](/docs_imagem/tagoio/rounded-image-1762433245481.png) Only certain integrations require an **Additional Parameter**. Check out the [list of integrations](/docs/tagoio/integrations/index.md) to learn the parameter diff --git a/docs/tagoio/integrations/general/creating-a-network-integration.md b/docs/tagoio/integrations/general/creating-a-network-integration.md index 68089443..613fd7f6 100644 --- a/docs/tagoio/integrations/general/creating-a-network-integration.md +++ b/docs/tagoio/integrations/general/creating-a-network-integration.md @@ -5,16 +5,12 @@ tags: ["tagoio", "integration"] sidebar_position: 1 --- -## Create a new integration +To create a new integration, go to the admin panel and click on the [Integrations](https://admin.tago.io/integrations/connector) button in the sidebar menu. +From there you can click on the "My Networks" on the menu on the right side of the page and finally click on the "Add network" button. -To create a new integration, go to the -[Network management page](https://admin.tago.io/integrations/network) and press -the Add network button on the right side of the page. +![Create a new integration](/docs_imagem/tagoio/rounded-image-1769101024685.png) -You only need to specify the network's name. For example, enter the name and -click "Create my Network". Once the network is created, you can configure -several optional parameters. If you want to keep the network private to your -account, you do not need to fill in all fields. +All you'll need to add is the network's name and click on the "Create my Network" button. Now you can configure the network's parameters by clicking on the "My networks" list. ## Parameters @@ -45,7 +41,7 @@ from different accounts. Read more about If you wish to make your connector or network accessible to all TagoIO users, you can request to make it public by submitting a Pull Request to our GitHub -repository: https://github.com/tago-io/decoders. +[repository](https://github.com/tago-io/decoders). ::: @@ -77,10 +73,9 @@ into the device. Device parameters let you set values that can later be accessed in the payload parser. They can be of type Number, Text, Dropdown, or Switch. -Example: A dropdown parameter appears in the user view as shown below (image -omitted for brevity). +Example: A "Payload Type" dropdown parameter appears in the user view as shown below. -![Dropdown parameter](/docs_imagem/tagoio/dropdown_parameter.png) +![Dropdown parameter](/docs_imagem/tagoio/rounded-image-1764012455142.png) For details on accessing these parameters in the payload parser, see the [Payload parser context overview](/docs/tagoio/devices/payload-parser/context-global-variables.md). diff --git a/docs/tagoio/integrations/index.md b/docs/tagoio/integrations/index.md index e8ef2ef4..82ea2916 100644 --- a/docs/tagoio/integrations/index.md +++ b/docs/tagoio/integrations/index.md @@ -21,7 +21,7 @@ from other protocols, by using one of the following methods: ## Device data flow -![Device data flow diagram](/docs_imagem/tagoio/connector-overview-2.png) +![Device data flow diagram](/docs_imagem/tagoio/devicedataflowupdated.png) ## Network Endpoints by Region diff --git a/docs/tagoio/integrations/networks/downlink-for-lorawan.md b/docs/tagoio/integrations/networks/downlink-for-lorawan.md index e9cb13f1..d73b2733 100644 --- a/docs/tagoio/integrations/networks/downlink-for-lorawan.md +++ b/docs/tagoio/integrations/networks/downlink-for-lorawan.md @@ -7,7 +7,7 @@ TagoIO will send downlink messages to your devices through Configuration Paramet :::warning -mportant: Most network servers require downlinks to be authenticated; otherwise they are denied access. If you're having problems sending downlinks, make sure you've correctly generated your [authorization codes](/docs/tagoio/integrations/general/authorization.md). +Important: Most network servers require downlinks to be authenticated; otherwise they are denied access. If you're having problems sending downlinks, make sure you've correctly generated your [authorization codes](/docs/tagoio/integrations/general/authorization.md). ::: diff --git a/docs/tagoio/integrations/networks/everynet-lorawan.md b/docs/tagoio/integrations/networks/everynet-lorawan.md index 8cb63712..7683e09c 100644 --- a/docs/tagoio/integrations/networks/everynet-lorawan.md +++ b/docs/tagoio/integrations/networks/everynet-lorawan.md @@ -11,7 +11,7 @@ TagoIO application. ## Connecting the platforms -![Everynet to TagoIO integration diagram](/docs_imagem/tagoio/everynet-lorawan-2.jpg) +![Everynet to TagoIO integration diagram](/docs_imagem/tagoio/rounded-image-1762437763780.png) ## Step 1: Create Authorization in TagoIO diff --git a/docs/tagoio/integrations/networks/loriot-lorawan.md b/docs/tagoio/integrations/networks/loriot-lorawan.md index fa8a1d47..e195aabe 100644 --- a/docs/tagoio/integrations/networks/loriot-lorawan.md +++ b/docs/tagoio/integrations/networks/loriot-lorawan.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- This tutorial provides a step-by-step guide to integrate Loriot LoRaWAN™ with the TagoIO Platform. By following these instructions, you will enable uplink and downlink operations, allowing data exchange between your LoRaWAN devices and the TagoIO application. -![Loriot scalable network to TagoIO integration diagram](/docs_imagem/tagoio/loriot-lorawan-2.png) +![Loriot scalable network to TagoIO integration diagram](/docs_imagem/tagoio/rounded-image-1762438126165.png) In order to complete the integration, follow the two steps below. @@ -15,8 +15,6 @@ In order to complete the integration, follow the two steps below. At the Loriot Console, open your Application and go to the **Access Token** section. -![Loriot Console — Authentication Tokens and Personalized Websocket URL](/docs_imagem/tagoio/loriot-lorawan-2.png) - Click on **Generate another authentication token**, a token will be generated. Copy the Authentication Token to use in the next step. ### Step 2: Create Authorization in TagoIO diff --git a/docs/tagoio/integrations/networks/machineq-lorawan.md b/docs/tagoio/integrations/networks/machineq-lorawan.md index e4ca7044..870f70c0 100644 --- a/docs/tagoio/integrations/networks/machineq-lorawan.md +++ b/docs/tagoio/integrations/networks/machineq-lorawan.md @@ -9,7 +9,7 @@ the TagoIO Platform. By following these instructions, you will enable both uplink and downlink operations, allowing data exchange between your LoRaWAN devices and the TagoIO application. -![machineQ to TagoIO integration diagram](/docs_imagem/tagoio/machineq-lorawan-2.png) +![machineQ to TagoIO integration diagram](/docs_imagem/tagoio/rounded-image-1762438254444.png) Follow these steps in order to integrate your devices. You may skip some steps depending on your situation. For example, if you have already generated an diff --git a/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio.md b/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio.md index 174c360f..916ab07d 100644 --- a/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio.md +++ b/docs/tagoio/integrations/networks/mqtt/connecting-your-mqtt-broker-to-tagoio.md @@ -26,8 +26,7 @@ tools such as the API and SDK. ## Installation -Learn how to use the relay here: -[tago-io/mqtt-relay: TagoIO | MQTT Relay](https://github.com/tago-io/mqtt-relay) +Learn how to use the relay by checking out the [TagoIO MQTT Relay GitHub repository](https://github.com/tago-io/mqtt-relay). ## How it works diff --git a/docs/tagoio/integrations/networks/mqtt/mqtt-process-data-publish-it-and-subscribe-to-a-topic.md b/docs/tagoio/integrations/networks/mqtt/mqtt-process-data-publish-it-and-subscribe-to-a-topic.md index 32a74df3..217f06f3 100644 --- a/docs/tagoio/integrations/networks/mqtt/mqtt-process-data-publish-it-and-subscribe-to-a-topic.md +++ b/docs/tagoio/integrations/networks/mqtt/mqtt-process-data-publish-it-and-subscribe-to-a-topic.md @@ -99,7 +99,7 @@ module.exports = new Analysis(mqttPushExample); This analysis requires permission to send MQTT data to the device. Enable this access in the **[Access Management](https://admin.tago.io/am)** module by creating a new **Policy**. -![MQTT Permission](/docs_imagem/tagoio/mqq_permission.png) +![MQTT Permission](/docs_imagem/tagoio/rounded-image-1762441866641.png) **Creating an Action** diff --git a/docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md b/docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md index cf05bb60..1935aaca 100644 --- a/docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md +++ b/docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md @@ -27,7 +27,7 @@ To build an MQTT **retain** workaround with TagoIO, you can either publish direc - In the action configuration, select **"MQTT Publish"** as the action type. - Specify the topic you wish to publish to and the message payload. -![Image 2](/docs_imagem/tagoio/external-41c105e7.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1769101281198.png) ## Using Analysis for Advanced Scenarios diff --git a/docs/tagoio/integrations/networks/orbiwise-lorawan.md b/docs/tagoio/integrations/networks/orbiwise-lorawan.md index 7e6b5b2f..370af3a1 100644 --- a/docs/tagoio/integrations/networks/orbiwise-lorawan.md +++ b/docs/tagoio/integrations/networks/orbiwise-lorawan.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- This tutorial provides a step-by-step guide to integrate **Orbiwise** LoRaWAN™ with the TagoIO Platform. By following these instructions, you will enable uplink and downlink operations, allowing data exchange between your LoRaWAN devices and the TagoIO application. -![Orbiwise and TagoIO integration diagram](/docs_imagem/tagoio/orbiwise-lorawan-2.jpg) +![Orbiwise and TagoIO integration diagram](/docs_imagem/tagoio/rounded-image-1762438341819.png) ## Prerequisites @@ -22,7 +22,7 @@ Before you begin, ensure you have the following: 2. **Create a New Authorization** 1. Click the **Create Authorization** button. - 2. Provide a meaningful name for the authorization (e.g., `MachineQ-Integration`). + 2. Provide a meaningful name for the authorization (e.g., `Orbiwise-Integration`). 3. In the **Additional Parameters** section, enter your Orbiwise Username, Password and DASS URL from Step 2 in the following format: ``` @@ -35,7 +35,7 @@ Before you begin, ensure you have the following: 3. **Copy the Authorization Token** - After creation, copy the authorization token. You will need this in later steps. -![Authorization token screenshot](/docs_imagem/tagoio/1563385125217-eok.png) +![Authorization token screenshot](/docs_imagem/tagoio/rounded-image-1762440792183.png) :::tip @@ -62,7 +62,7 @@ Only one **Authorization** per application is necessary. Don't do it for each de 3. **Start Push** - Make sure that you set the status of your Application to **<Start Push>**. -![Orbiwise backend configuration](/docs_imagem/tagoio/oribiwse_backend_config-a9U.png) +![Orbiwise backend configuration](/docs_imagem/tagoio/rounded-image-1769101996090.png) diff --git a/docs/tagoio/integrations/networks/senet-network.md b/docs/tagoio/integrations/networks/senet-network.md index e45dfc4d..dd854af7 100644 --- a/docs/tagoio/integrations/networks/senet-network.md +++ b/docs/tagoio/integrations/networks/senet-network.md @@ -20,8 +20,6 @@ The integration is accomplished in two parts: First, go to the [Devices](/docs/tagoio/devices/) module in our admin, look for Senet, and select it. -![Connector selection showing the Senet connector in the Devices module](/docs_imagem/tagoio/senet-network-4.png) - ### Create Device Type a name for your device, select a @@ -29,7 +27,7 @@ Type a name for your device, select a **[Data Retention](/docs/tagoio/devices/data-management/data-retention-feature.md)**, then click on _Create device_. -![Device creation screen](/docs_imagem/tagoio/external-00c113a0.png) +![Device creation screen](/docs_imagem/tagoio/rounded-image-1762441561759.png) ### Generate Service Authorization @@ -47,7 +45,7 @@ Now, log in to **[Senet portal](http://portal.senetco.io/)** and go to your devices.\ Choose the device to connect to TagoIO and click on the gear icon. -![Senet device settings](/docs_imagem/tagoio/senet-network-4.png) +![Senet device settings](/docs_imagem/tagoio/rounded-image-1769102832066.png) Go to **"Notification Target"**. Make sure the status is _Enabled_, select **HTTP** in the 'forward to' field, and fill the fields accordingly: @@ -59,7 +57,7 @@ Go to **"Notification Target"**. Make sure the status is _Enabled_, select | **Headers** | Add a header key `Authorization` and set its value to the authorization token you copied in Step 1. | | **Optional Data Fields** | Enable _RF Data_ and any other optional field you would like to receive in your device. | -![Notification Target configuration](/docs_imagem/tagoio/external-b2ca369e.png) +![Notification Target configuration](/docs_imagem/tagoio/rounded-image-1769102866603.png) ### Setting up Downlink @@ -74,7 +72,7 @@ In order to support downlinks from TagoIO to Senet, you need an additional step. 3. Click to edit the **Additional Parameters** of the Authorization. 4. Paste your Developer API Key and press _Save_. -![Developer API Key configuration](/docs_imagem/tagoio/external-969e5674.png) +![Developer API Key configuration](/docs_imagem/tagoio/rounded-image-1762441641103.png) Now you are all set; every time your device sends data to Senet, your data will be available at TagoIO. diff --git a/docs/tagoio/integrations/networks/senra-network.md b/docs/tagoio/integrations/networks/senra-network.md index d32bb87e..c9b5f11c 100644 --- a/docs/tagoio/integrations/networks/senra-network.md +++ b/docs/tagoio/integrations/networks/senra-network.md @@ -14,7 +14,7 @@ The integration is accomplished in two parts: 1. Go to the [devices](/docs/tagoio/devices/) section, search for "SenRa", and select it. 2. Type a name for your device and click "Create device". -![TagoIO device creation screen](/docs_imagem/tagoio/senra-network-2.png) +![senra device settings](/docs_imagem/tagoio/rounded-image-1769102191287.png) 3. Access the device you just created, open the "Token" tab, and copy the `device-token`. You will use this token in the next step. diff --git a/docs/tagoio/integrations/networks/sigfox/sigfox-downlink.md b/docs/tagoio/integrations/networks/sigfox/sigfox-downlink.md index ee3b6658..f0046f87 100644 --- a/docs/tagoio/integrations/networks/sigfox/sigfox-downlink.md +++ b/docs/tagoio/integrations/networks/sigfox/sigfox-downlink.md @@ -18,7 +18,7 @@ accurately authenticate your downlink. ::: -![Downlink diagram](/docs_imagem/tagoio/sigfox-downlink-2.png) +![Downlink diagram](/docs_imagem/tagoio/rounded-image-1762441468085.png) Downlink Diagram diff --git a/docs/tagoio/integrations/networks/sigfox/sigfox.md b/docs/tagoio/integrations/networks/sigfox/sigfox.md index f30d554e..81c910b3 100644 --- a/docs/tagoio/integrations/networks/sigfox/sigfox.md +++ b/docs/tagoio/integrations/networks/sigfox/sigfox.md @@ -14,7 +14,7 @@ platform. By following these instructions, you will enable uplink and downlink operations, allowing data exchange between your Sigfox devices and the TagoIO application. -![Sigfox architecture diagram showing Modules → Sigfox stations → Sigfox Cloud™ → TagoIO (Uplink / Downlink flows)](/docs_imagem/tagoio/sigfox-2.png) +![Sigfox architecture diagram showing Modules → Sigfox stations → Sigfox Cloud™ → TagoIO (Uplink / Downlink flows)](/docs_imagem/tagoio/rounded-image-1762441353390.png) Uplink is the process of sending data from the devices to TagoIO. Downlink is used to send data back to the devices. Learn how to perform diff --git a/docs/tagoio/integrations/networks/the-things-network-lorawan.md b/docs/tagoio/integrations/networks/the-things-network-lorawan.md index 67374858..a410e392 100644 --- a/docs/tagoio/integrations/networks/the-things-network-lorawan.md +++ b/docs/tagoio/integrations/networks/the-things-network-lorawan.md @@ -13,7 +13,7 @@ devices and the TagoIO application. > [TTI integration](https://community.tago.io/t/how-to-integrate-tagoio-with-ttn-v3/1026) > instructions. -![Integration diagram showing LoRaWAN devices, The Things Network, a connector, and TagoIO](/docs_imagem/tagoio/the-things-network-lorawan-2.png) +![Integration diagram showing LoRaWAN devices, The Things Network, a connector, and TagoIO](/docs_imagem/tagoio/rounded-image-1762440999827.png) ## Prerequisites @@ -34,7 +34,7 @@ Before you begin, ensure you have the following: 3. Provide a meaningful name for the authorization (e.g., `TTN-Integration`). 4. Click **Save**. -![Image 2](/docs_imagem/tagoio/external-122ff21d.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1762441089626.png) ### Copy the Authorization Token @@ -46,7 +46,7 @@ After creation, copy the authorization token. You will need this in later steps. 2. Go to **Integrations > Webhook > + Add Webhook**. 3. Select **Custom Webhook** from the list. -![Image 3](/docs_imagem/tagoio/tagoIO_ttn-WUw.png) +![Image 3](/docs_imagem/tagoio/rounded-image-1762441177206.png) ### Webhook Configuration @@ -58,7 +58,7 @@ After creation, copy the authorization token. You will need this in later steps. | **Additional Headers** | Add a header key `Authorization` and set its value to the authorization token you copied in Step 1. | | **Enabled event types** | Enable the event types you expect to receive from your device. Set the path of all enabled event types to `/uplink`. | -![Image 4](/docs_imagem/tagoio/external-eae39401.png) +![Image 4](/docs_imagem/tagoio/rounded-image-1762441267639.png) ## Step 3: Add Your Device to TagoIO diff --git a/docs/tagoio/my-account/billing/account-plans.md b/docs/tagoio/my-account/billing/account-plans.md index bc23786d..cb76dd89 100644 --- a/docs/tagoio/my-account/billing/account-plans.md +++ b/docs/tagoio/my-account/billing/account-plans.md @@ -5,7 +5,7 @@ tags: ["tagoio", "billing"] --- ## Overview -TagoIO offers three account plans that allow you to use the platform's tools and capabilities for your application. Select your plan on the [My Billing](https://admin.tago.io/account/billing) page. +TagoIO offers three account plans that allow you to use the platform's tools and capabilities for your application. Select your plan in the [My Billing](https://admin.tago.io/account/billing) page. ### Plan Types diff --git a/docs/tagoio/my-account/billing/allocating-services-to-profiles.md b/docs/tagoio/my-account/billing/allocating-services-to-profiles.md index 71a4412a..020b70e8 100644 --- a/docs/tagoio/my-account/billing/allocating-services-to-profiles.md +++ b/docs/tagoio/my-account/billing/allocating-services-to-profiles.md @@ -24,7 +24,7 @@ You can easily monitor the amount of resources available in your account that ca On the left side, the 'Account Service Allocation' column shows the total service amounts available for distribution across your account. These are the limits you've set for your entire account, which can be increased by clicking the 'Upgrade account limits' button or through the [Billing](https://admin.tago.io/account/billing) page in the 'Services' tab. -On the right, 'Profile Usage Allocation' show how much of each service has been used by each profile, highlighting which profiles are close to or have reached their limits. Clicking on a resource opens a new window for customizing its allocation. +On the right, 'Profile Usage Allocation' shows how much of each service has been used by each profile, highlighting which profiles are close to or have reached their limits. Clicking on a resource opens a new window for customizing its allocation. ![Resource allocation graph](/docs_imagem/tagoio/resource_allocation_profile.png) diff --git a/docs/tagoio/my-account/billing/common-billing-issues.md b/docs/tagoio/my-account/billing/common-billing-issues.md index 240b6549..614aa1fe 100644 --- a/docs/tagoio/my-account/billing/common-billing-issues.md +++ b/docs/tagoio/my-account/billing/common-billing-issues.md @@ -7,7 +7,7 @@ tags: ["tagoio"] Declines can occur for many reasons determined by the cardholder’s bank. Each bank uses a system that considers various signals, such as the cardholder’s spending habits, account balance, and card information like the expiration date and CVV/CVC security number. -Since these signals change over time, a card that was previously successful may be declined for a future charge. +Since these signals change over time, a card that was previously successful may be declined for future charges. :::info @@ -17,7 +17,7 @@ Even if all card information is correct and the cardholder previously had a succ ## Finding out more information about a specific decline -TagoIO displays all information we receive from the cardholder’s bank and the payment processor about a decline in the error message. Because of this, we do not have additional details beyond the error information provided to us. +TagoIO displays all information we receive from the cardholder's bank and the payment processor about a decline in the error message. Because of this, we do not have additional details beyond what is provided to us. :::info @@ -43,5 +43,5 @@ The cardholder’s bank is the entity declining the charge and sending the error “Your card has insufficient funds.” - The cardholder's bank is saying that they don't have enough funds in their account to cover the costs of the purchase. -- Sometimes cardholders banks don't properly assess the risk of currency conversion of purchases. If they see that the purchase is in a different currency the bank will decline the charge as insufficient funds so the currency conversion or the currency conversion fee doesn't overdraw the account. +- Sometimes cardholder's banks don't properly assess the risk of currency conversion for purchases. If they see that the purchase is in a different currency, the bank will decline the charge as insufficient funds so that the currency conversion or the currency conversion fee doesn't overdraw the account. - If a cardholder sees this error message, they should contact their bank. \ No newline at end of file diff --git a/docs/tagoio/my-account/billing/downgrading-plans-services.md b/docs/tagoio/my-account/billing/downgrading-plans-services.md index 3754875b..c4819086 100644 --- a/docs/tagoio/my-account/billing/downgrading-plans-services.md +++ b/docs/tagoio/my-account/billing/downgrading-plans-services.md @@ -20,7 +20,7 @@ If you change your mind any time before the end of the billing cycle, you can mo If you have more than one profile, make sure you manually [reduce the resources for each profile](/docs/tagoio/my-account/billing/allocating-services-to-profiles.md) before your next billing cycle to avoid any disruption to your application. ## How to downgrade -To downgrade your billing, go to [Billing](https://admin.tago.io/account/billing) on the top-right dropdown menu in your account. +To downgrade your billing, click on your account name at the bottom-left menu in your Admin, hover over "Profiles & Billing" and select **[Billing](https://admin.tago.io/account/billing)** option. ## Refunds See our [Refund Policy](/docs/tagoio/my-account/billing/refund-policy.md). diff --git a/docs/tagoio/my-account/billing/refund-policy.md b/docs/tagoio/my-account/billing/refund-policy.md index 142cc1c2..d477cac8 100644 --- a/docs/tagoio/my-account/billing/refund-policy.md +++ b/docs/tagoio/my-account/billing/refund-policy.md @@ -22,6 +22,6 @@ You may be entitled to a refund in the following cases: :::info -When a payment method different from credit card is used, there may be an additional bank or processing fee associated with the refund process. +When a payment method other than a credit card is used, there may be an additional bank or processing fee associated with the refund process. ::: diff --git a/docs/tagoio/my-account/billing/resource-limits.md b/docs/tagoio/my-account/billing/resource-limits.md index 54357e4e..b38490a4 100644 --- a/docs/tagoio/my-account/billing/resource-limits.md +++ b/docs/tagoio/my-account/billing/resource-limits.md @@ -49,6 +49,6 @@ plans and services, check our [Pricing Page](https://tago.io/pricing). ## Monitoring resources across your entire account -You can monitor the amount of resources you have used by accessing the account -menu in the top right corner of your Admin page and selecting the +You can monitor the amount of resources you have used by accessing the profile +menu in the top left corner of your Admin page and selecting the **[Hard Limits](https://admin.tago.io/limits/hard)** option. diff --git a/docs/tagoio/my-account/billing/setup-billing.md b/docs/tagoio/my-account/billing/setup-billing.md index cc163902..c9449f89 100644 --- a/docs/tagoio/my-account/billing/setup-billing.md +++ b/docs/tagoio/my-account/billing/setup-billing.md @@ -3,7 +3,7 @@ title: "Setup Billing" description: "This article explains how to access and configure your billing settings in TagoIO, including where to add company and payment information and how to select an account plan." tags: ["tagoio"] --- -To set up your billing, open the top‑right account menu (just under your avatar) and click the **[Billing](https://admin.tago.io/account/billing** option. +To set up your billing, click on your account name at the bottom-left menu in your Admin, hover over "Profiles & Billing" and select **[Billing](https://admin.tago.io/account/billing)** option. diff --git a/docs/tagoio/my-account/billing/upgrading-plans-services.md b/docs/tagoio/my-account/billing/upgrading-plans-services.md index e0228d73..0e6919ea 100644 --- a/docs/tagoio/my-account/billing/upgrading-plans-services.md +++ b/docs/tagoio/my-account/billing/upgrading-plans-services.md @@ -17,7 +17,7 @@ Some services are not prorated if they are consumable. For example, if you incre ::: -To upgrade your billing, go to the [Billing](https://admin.tago.io/account/billing) option in the top‑right dropdown menu. +To upgrade your billing, click on your account name at the bottom-left menu in your Admin, hover over "Profiles & Billing" and select **[Billing](https://admin.tago.io/account/billing)** option. ## How to auto-scale diff --git a/docs/tagoio/my-account/deleting-your-account.md b/docs/tagoio/my-account/deleting-your-account.md index d10861f0..9db1f5d2 100644 --- a/docs/tagoio/my-account/deleting-your-account.md +++ b/docs/tagoio/my-account/deleting-your-account.md @@ -5,11 +5,12 @@ tags: ["tagoio"] --- ## How to delete your account -If you need to cancel your account, go to Account Settings by accessing [My Account](https://admin.tago.io/account). +If you need to cancel your account, go to Account Settings by accessing [My Account](https://admin.tago.io/account/general). Steps: -- Open Account Settings via [My Account](https://admin.tago.io/account). -- In the Account Settings, open the "More" tab and click the `delete my account` button. +- Click on your account name at the bottom-left menu in your Admin and select "My Account". +- Hover over "Profiles & Billing" and select "My Account". +- On the top right corner click "... Account Details" and click the "Delete my account" button. - TagoIO will delete your account, including all profiles associated with it, and will send a confirmation email when the deletion is complete. :::warning diff --git a/docs/tagoio/my-account/index.md b/docs/tagoio/my-account/index.md index 8c1a6a7c..3558bb0e 100644 --- a/docs/tagoio/my-account/index.md +++ b/docs/tagoio/my-account/index.md @@ -4,10 +4,7 @@ description: "This article explains how to open the account settings in TagoIO a tags: ["tagoio"] --- ## Accessing your account settings -To manage your account details, click the top-right menu in the TagoIO interface and select the option [My Account](https://admin.tago.io/account/). - -The avatar shown in the top right corner represents the profile picture linked to your email address. If you don't currently have one, you can create an avatar using [Gravatar](https://en.gravatar.com/). - +To manage your account details, click the bottom-left menu in the TagoIO interface and hover over "Profiles & Billing" and select the option [My Account](https://admin.tago.io/account/general). ## What you can edit From the Account settings page you can edit various personal and account preferences, including: diff --git a/docs/tagoio/my-account/managing-your-account-with-the-tagoio-mobile-app.md b/docs/tagoio/my-account/managing-your-account-with-the-tagoio-mobile-app.md index b985ce35..cbfcfa2e 100644 --- a/docs/tagoio/my-account/managing-your-account-with-the-tagoio-mobile-app.md +++ b/docs/tagoio/my-account/managing-your-account-with-the-tagoio-mobile-app.md @@ -4,11 +4,9 @@ description: "A brief guide to the TagoIO Mobile App, describing how it helps yo tags: ["tagoio"] sidebar_position: 1 --- -The TagoIO App is your gateway to streamlining your ecosystem and managing all your IoT applications in one place. It enables you to monitor and control services and resources across all your profiles, and receive real‑time notifications and alerts on your smartphone so you stay informed about activities. +The TagoIO App is your gateway to streamlining your ecosystem and managing all your IoT applications in one place. It enables you to monitor and control services and resources across all your profiles and receive real‑time notifications and alerts on your smartphone so you stay informed about activities. -It allows you to monitor and control your services and resources for all your profiles. Receive real‑time notifications and alerts on your smartphone, staying informed about all activities. - -![TagoIO App](/docs_imagem/tagoio/external-93280f88.png) +![TagoIO App](/docs_imagem/tagoio/rounded-image-1769103991697.png) ## Download Download the TagoIO App from the App Store (iOS) or Google Play (Android). diff --git a/docs/tagoio/my-account/resetting-my-password.md b/docs/tagoio/my-account/resetting-my-password.md index 4046ec0b..71cb5159 100644 --- a/docs/tagoio/my-account/resetting-my-password.md +++ b/docs/tagoio/my-account/resetting-my-password.md @@ -8,10 +8,12 @@ On the [signup page](https://admin.tago.io/signup), click the "Forgot your passw ## Want to change your password? To change your existing password: -- Go to [My Account](https://admin.tago.io/account). -- Select the "Account Settings" tab. -- Click the "Change your password" button and follow the prompts. +- Click on your account name at the bottom-left menu in your Admin. +- Hover over "Profiles & Billing" and select "My Account". +- Go to the [Security](https://admin.tago.io/account/security) tab. +- Click the "Change password" button and follow the prompts. +![Forgot your password?](/docs_imagem/tagoio/rounded-image-1761224471130.png) :::tip diff --git a/docs/tagoio/my-account/two-factor-authentication-2fa.md b/docs/tagoio/my-account/two-factor-authentication-2fa.md index 2a55e4f9..c8785001 100644 --- a/docs/tagoio/my-account/two-factor-authentication-2fa.md +++ b/docs/tagoio/my-account/two-factor-authentication-2fa.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- Two-factor authentication (2FA) adds an extra layer of security to your account by requiring more than just your password to sign in. It requires and provides another form of authentication that only you know or have access to. -![Two-factor methods list](/docs_imagem/tagoio/two-factor-authentication-2fa-2.png) +![Two-factor methods list](/docs_imagem/tagoio/rounded-image-1761224381413.png) ## Available authentication methods - App Authenticator — a six-digit code generated by an authentication app on your mobile device (for example, Google Authenticator, Authy). diff --git a/docs/tagoio/profiles/account-token.md b/docs/tagoio/profiles/account-token.md index 9a47c316..e075dc0e 100644 --- a/docs/tagoio/profiles/account-token.md +++ b/docs/tagoio/profiles/account-token.md @@ -3,7 +3,7 @@ title: "Account Token" description: "This article explains what Account Tokens are in TagoIO, why they must be kept secret, and how to manage them from your account profile. It also highlights that multiple tokens can be created with configurable permissions and expiration." tags: ["tagoio"] --- -Account Tokens are the secret keys used between Tago and external applications. Any access from an account requires a valid token, so it is vital that tokens are kept secret and only shared with trusted parties. +Account Tokens are the secret keys used between TagoIO and external applications. Any access from an account requires a valid token, so it is vital that tokens are kept secret and only shared with trusted parties. :::warning diff --git a/docs/tagoio/profiles/audit-log.md b/docs/tagoio/profiles/audit-log.md index 0adc2d5b..0f074da8 100644 --- a/docs/tagoio/profiles/audit-log.md +++ b/docs/tagoio/profiles/audit-log.md @@ -21,7 +21,7 @@ Each action executed by an agent on a resource is considered an event. Agents ca TagoIO keeps a 6‑month log for each profile; events older than that will not be displayed. -![Event overview](/docs_imagem/tagoio/external-d3b441c9.png) +![Event overview](/docs_imagem/tagoio/rounded-image-1761078341385.png) :::info @@ -51,7 +51,7 @@ Search for an event tied to a specific resource by its ID. If you choose a Resou ### Event messages Each event includes a message describing the action performed on the resource. You can filter events based on these messages. -![Event message example](/docs_imagem/tagoio/external-f91f78f4.png) +![Event message example](/docs_imagem/tagoio/rounded-image-1761078136729.png) ## Automation diff --git a/docs/tagoio/profiles/index.md b/docs/tagoio/profiles/index.md index 485da3c2..abf3de5d 100644 --- a/docs/tagoio/profiles/index.md +++ b/docs/tagoio/profiles/index.md @@ -20,18 +20,17 @@ Profiles are similar to having different sub-accounts under your main account. Y To switch profiles, click the current profile shown on the top left and select another one. - - +![Switching Profiles](/docs_imagem/tagoio/rounded-image-1761227083363.png) ## Adding Profiles -Go to your account, select **[Profiles & Teams](https://admin.tago.io/profile)** from the list, and click on **Add Profile**. +Go to your account menu on the bottom left corner, hover over "Profiles & Billing" and select **[Profiles & Teams](https://admin.tago.io/profile)** from the list, and click on **Add Profile**. After that, you can edit the profile to change the name, logo, and upgrade services & add‑ons for it. Each profile starts with certain services included; you can increase the limits as you scale up the applications that run on that profile. ## Renaming Your Profiles -Navigate to your **[Profiles & Teams](https://admin.tago.io/profile)** page and select the **Profile** tab. Click on the profile name, type a new one, and click **Save** to finalize your changes. It is possible to use the exact same name for multiple profiles. +Navigate to your **[Profiles & Teams](https://admin.tago.io/profile)** page and select the **Profile** tab. Click on the profile name, type a new one. It is possible to use the same name for multiple profiles. ### Sharing Profiles with Teams @@ -51,10 +50,10 @@ Add others to your profiles by adding their e‑mails in the team section. To in Once you request a transfer, our support team will assist you with the next steps. When you submit a profile transfer request, a support ticket is automatically created, and our team will contact you by email to confirm required information and prerequisites before proceeding with the transfer. The process is manual and may take a few hours to complete. -You can request the profile transfer by navigating to [Profiles](https://admin.tago.io/profile) > More > and clicking on "Transfer this profile to another account", then typing the Account E-mail of the destination account in the field shown below: +You can request the profile transfer by navigating to [Profiles](https://admin.tago.io/profile) > ... Profile Preferences > and clicking on "Transfer to another account", then typing the Account E-mail of the destination account in the field shown below: :::info -Profile transfer is available for Starter and Scale accounts. Check the pricing page for more information: https://tago.io/pricing/ +Profile transfer is available for Starter and Scale accounts. Check the [pricing page](https://tago.io/pricing/) for more information. ::: diff --git a/docs/tagoio/profiles/services/analysis-service.md b/docs/tagoio/profiles/services/analysis-service.md index f4cc7741..f8d2ab98 100644 --- a/docs/tagoio/profiles/services/analysis-service.md +++ b/docs/tagoio/profiles/services/analysis-service.md @@ -20,7 +20,7 @@ to run your Analyses. It is safer to add some extra time to account for time var Only scripts that are configured to run on TagoIO are counted. Scripts that run from "External" do not count. -![Run this script from options (TagoIO / External)](/docs_imagem/tagoio/analysis-service-2.png) +![Run this script from options (TagoIO / External)](/docs_imagem/tagoio/rounded-image-1762263701444.png) :::warning diff --git a/docs/tagoio/profiles/services/data-input-service.md b/docs/tagoio/profiles/services/data-input-service.md index 65c56f4e..66f6fd4e 100644 --- a/docs/tagoio/profiles/services/data-input-service.md +++ b/docs/tagoio/profiles/services/data-input-service.md @@ -38,4 +38,4 @@ Rate limits are applied to a wide range of interactions within the platform, inc ## Viewing limits and usage history You can visualize the limits and usage history of each service in the Profile tab, located under the [Profiles & Teams](https://admin.tago.io/profile) section of your account. -![Image 1](/docs_imagem/tagoio/external-f4bf5eb6.png) +![Image 1](/docs_imagem/tagoio/rounded-image-1762263846752.png) diff --git a/docs/tagoio/profiles/services/data-records.md b/docs/tagoio/profiles/services/data-records.md index 9ebd9123..2cc156f8 100644 --- a/docs/tagoio/profiles/services/data-records.md +++ b/docs/tagoio/profiles/services/data-records.md @@ -32,7 +32,7 @@ All fields and [metadata](/docs/tagoio/devices/payload-parser/metadata.md) store ] ``` -Another simple example: Your device sends speed, temperature, and humidity with location every 1hour. As a result, 3 new registers will be added every hour. +Another simple example: Your device sends speed, temperature, and humidity with location every hour. As a result, 3 new registers will be added every hour. ## Notes diff --git a/docs/tagoio/profiles/services/rate-limits-hard-limits.md b/docs/tagoio/profiles/services/rate-limits-hard-limits.md index e789315c..4bb088ad 100644 --- a/docs/tagoio/profiles/services/rate-limits-hard-limits.md +++ b/docs/tagoio/profiles/services/rate-limits-hard-limits.md @@ -9,7 +9,7 @@ Rate limits apply to a wide range of interactions within the platform, including :::note -Hard limits are used to prevent high-frequency usage beyond a healthy acceptable level; this is different from [TagoIO services](/docs/tagoio/profiles/services/) that are reset monthly. You still need to make sure you have enough resources to run your application. +Hard limits are used to prevent high-frequency usage beyond a healthy acceptable level; this is different than [TagoIO services](/docs/tagoio/profiles/services/) that are reset monthly. You still need to make sure you have enough resources to run your application. ::: @@ -29,7 +29,7 @@ The system aggregates all requests performed inside a Profile for each route. Th :::tip -Check our [Control Tower add‑on](/docs/tagoio/addons/control-tower.md). +Check out the [Control Tower add‑on](/docs/tagoio/addons/control-tower.md). ::: @@ -127,12 +127,8 @@ When a hard limit has been exceeded, TagoIO will return an **HTTP 429 “Too Man { "status": false, "message": "Too many requests (Retry-After: 8)" } ``` -When using the Admin, the following error will be displayed: - -![Image](/docs_imagem/tagoio/external-bf3190c0.png) - If you need help adapting your project to these hard limits, try our [Community](https://community.tago.io/). ## Rate limits usage monitoring -You can monitor the hard limits for each function by accessing the account menu located in the top right corner of your [Admin](https://admin.tago.io/limits/hard) page and selecting the **Hard Limits** option. If the [Control Tower](/docs/tagoio/addons/control-tower.md) add‑on is active in your account, you will have the ability to view historical and detailed statistics of your usage for Hard Limits, providing insights into your requests per minute. +You can monitor the hard limits for each function by accessing the profile menu located in the top left corner of your [Admin](https://admin.tago.io/limits/hard) page and selecting the **Hard Limits** option. If the [Control Tower](/docs/tagoio/addons/control-tower.md) add‑on is active in your account, you will have the ability to view historical and detailed statistics of your usage for Hard Limits, providing insights into your requests per minute. diff --git a/docs/tagoio/profiles/services/sms-service.md b/docs/tagoio/profiles/services/sms-service.md index af8cd243..e853c4d1 100644 --- a/docs/tagoio/profiles/services/sms-service.md +++ b/docs/tagoio/profiles/services/sms-service.md @@ -17,7 +17,7 @@ As anticipated, starting on **November 1st, 2024**, TagoIO will no longer offer - If the SMS service limit is exceeded, no SMS for that Profile will be sent until the limit is increased or the billing period ends. -- SMS pricing is only valid for: United States, Australia, Germany, United Kingdom, Canada, Mexico, Brasil, Colombia, Japan, and Chile. For other countries, contact us. +- SMS pricing is only valid for: United States, Australia, Germany, United Kingdom, Canada, Mexico, Brazil, Colombia, Japan, and Chile. For other countries, contact us. - SMS messages not used during the period will not be carried over to the next month. - For more information on pricing and FAQs, see the [Pricing Page](https://tago.io/pricing/). diff --git a/docs/tagoio/profiles/services/usage-policy.md b/docs/tagoio/profiles/services/usage-policy.md index 4a17579a..7d596e12 100644 --- a/docs/tagoio/profiles/services/usage-policy.md +++ b/docs/tagoio/profiles/services/usage-policy.md @@ -7,7 +7,7 @@ When executing API requests to TagoIO — either posting (data input) or getting ## How limits work - Limits are based on the number of transactions allowed for a given time period (for example, per hour or per minute). -- A global (higher-level) limit is also applied to all accounts to help prevent attacks on TagoIO servers (for example, DDoS) and to provide a way to limit usage from applications. +- A global (higher-level) limit is also applied to all accounts to help prevent attacks on TagoIO servers (for example, DDoS attacks) and to provide a way to limit usage from applications. >Check our comprehensive documentation on [Rate Limits](/docs/tagoio/profiles/services/rate-limits-hard-limits.md). diff --git a/docs/tagoio/profiles/team-management-sharing-your-profile.md b/docs/tagoio/profiles/team-management-sharing-your-profile.md index 21aadfb8..795bcdf0 100644 --- a/docs/tagoio/profiles/team-management-sharing-your-profile.md +++ b/docs/tagoio/profiles/team-management-sharing-your-profile.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- You can grant access to other TagoIO accounts to any of your [Profiles](/docs/tagoio/profiles/) by using the Team feature. By adding other accounts to your team, they will have access to all applications that run on that Profile. - +![Team Management - Sharing your profile](/docs_imagem/tagoio/rounded-image-1762263403092.png) ## Invitation notification The invitation can only be sent to email addresses that already have a TagoIO account. If the invited user doesn't have an account, the invitation email will guide them to create one. diff --git a/docs/tagoio/support/_category_.json b/docs/tagoio/support/_category_.json deleted file mode 100644 index 23406c37..00000000 --- a/docs/tagoio/support/_category_.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "label": "Support", - "position": 20, - "collapsed": true -} diff --git a/docs/tagoio/support/ticket-severity-options.md b/docs/tagoio/support/ticket-severity-options.md deleted file mode 100644 index 5ced9b99..00000000 --- a/docs/tagoio/support/ticket-severity-options.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: "Ticket Severity Options" -description: "This article defines the TagoIO Support ticket severity levels and explains how to select the appropriate priority when opening a support ticket." -tags: ["tagoio"] ---- - -In order for your ticket to receive the correct priority, select the appropriate severity level when opening the ticket. The TagoIO Support team recommends following these definitions to avoid delays. - -:::info - -Our team reserves the right to correct any severity level that was incorrectly selected. - -::: - -Our support team uses the following definitions to classify issues: - -### Severity 1 — Critical Impact / Complete Outage -A problem that severely impacts your use of the application in a production environment. This indicates an inability to access your application or perform all critical functions. The situation halts your business operations and **no procedural workaround exists**. - -### Severity 2 — Significant Business Impact -A problem where the service is functioning but its use in the production environment is severely reduced. A major feature or function is restricted, and because a procedural workaround is not available, your business is highly impacted. - -### Severity 3 — Minor Impact -A problem that causes partial degradation of system performance or a non‑critical loss of application functionality. A workaround is available, and the system remains usable for normal business operations. - -### Severity 4 — No Business Impact / General Question -Questions about configuration, feature requests, or general usage assistance. These issues do not affect production operations and have no significant business impact. - -Notice that response times are based on your current TagoIO plan and the Support plan associated with it. Learn more about [Support Plan](https://tago.io/support-plans/). \ No newline at end of file diff --git a/docs/tagoio/tagorun/access-management/creating-a-policy.md b/docs/tagoio/tagorun/access-management/creating-a-policy.md index 7583b7a5..5b9eeaaf 100644 --- a/docs/tagoio/tagorun/access-management/creating-a-policy.md +++ b/docs/tagoio/tagorun/access-management/creating-a-policy.md @@ -6,9 +6,9 @@ sidebar_position: 2 --- You can create individual policies to securely grant access to specific resources in your account for pre-defined targets. -You create [Targets](/docs/tagoio/tagorun/access-management/defining-targets.md) (for example, users) and decide which resource types they can access by assigning [Permissions](/docs/tagoio/tagorun/access-management/defining-permissions.md) (for example, dashboards). +You create [Targets](/docs/tagoio/tagorun/access-management/defining-targets.md) and decide which resource types they can access by assigning [Permissions](/docs/tagoio/tagorun/access-management/defining-permissions.md). To do this, navigate to the [Access module](https://admin.tago.io/am) and click **Add Policy**. -![Access Management — policy list and Add Policy button](/docs_imagem/tagoio/creating-a-policy-2.png) +![Access Management — policy list and Add Policy button](/docs_imagem/tagoio/rounded-image-1761226314440.png) diff --git a/docs/tagoio/tagorun/access-management/defining-permissions.md b/docs/tagoio/tagorun/access-management/defining-permissions.md index 8ea7953c..1d8b46ca 100644 --- a/docs/tagoio/tagorun/access-management/defining-permissions.md +++ b/docs/tagoio/tagorun/access-management/defining-permissions.md @@ -6,15 +6,15 @@ sidebar_position: 4 --- You need to set up Permissions to define which types of resources your Targets will be allowed or denied access to. -The resources available to grant permission depend on the Target you select, and the rules available depend on the resource selected. See [Defining Targets](/docs/tagoio/tagorun/access-management/defining-targets.md). +The resources available to grant permission depend on the Target you select, and the rules available depend on the resource selected. For more information, see [Defining Targets](/docs/tagoio/tagorun/access-management/defining-targets.md). -![Permissions editor showing Targets and Permissions](/docs_imagem/tagoio/defining-permissions-2.png) +![Permissions editor showing Targets and Permissions](/docs_imagem/tagoio/rounded-image-1761226750000.png) ## Adding resources and how rules are applied You can add as many resources as needed. An OR operation is applied between permissions: as you add more permissions, more resources will be included in the verification process. :::warning -If you use one permission with Deny, it will override any options using an Allow that contain the same condition. +Denial permissions will override any permissions granting access to the same resource. ::: diff --git a/docs/tagoio/tagorun/access-management/defining-targets.md b/docs/tagoio/tagorun/access-management/defining-targets.md index 84e61598..2121895d 100644 --- a/docs/tagoio/tagorun/access-management/defining-targets.md +++ b/docs/tagoio/tagorun/access-management/defining-targets.md @@ -4,8 +4,8 @@ description: "This article explains how to define Targets within a policy in the tags: ["tagoio"] sidebar_position: 3 --- -You should define **Targets** in each policy that are used inside the [Access Management](https://admin.tago.io/am) module. Targets can be users or things (for example, [scripts](/docs/tagoio/analysis/)). +You can define multiple **Targets** in each policy that are used inside the [Access Management](https://admin.tago.io/am) module. :::tip Targets are to whom or to what you are giving the permissions. @@ -14,7 +14,7 @@ Targets are to whom or to what you are giving the permissions. Currently, you can select [Run Users](/docs/tagoio/profiles/services/end-users-service.md) and [Analysis](/docs/tagoio/analysis/) as Targets. -![Targets configuration example](/docs_imagem/tagoio/defining-targets-2.png) +![Targets configuration example](/docs_imagem/tagoio/rounded-image-1761226494988.png) ## How multiple Targets work You can add more Targets of the same type as needed. Multiple Targets are combined using a logical OR, so adding more targets makes the resulting options more inclusive. For example: @@ -22,9 +22,9 @@ You can add more Targets of the same type as needed. Multiple Targets are combin ## Target Matching Options -Target matching can be performed in several ways: +Selecting a Target can be performed in several ways: -1. **ID** – select a target from the list. +1. **ID** – select a specific target from the list. 2. **Tag** – match using tags from your target. Learn more about the [Tags System](/docs/tagoio/getting-started/tags-system.md). @@ -34,12 +34,12 @@ Target matching can be performed in several ways: 3. **Tag Match** – the match is automatically by searching for those Tag Keys of the selected target. - Run User: tag keys presented in your users will be listed. - - Analysis: only tag keys presented in your [Analysis](/docs/tagoio/analysis/) will be listed. + - Analysis: tag keys presented in your [Analysis](/docs/tagoio/analysis/) will be listed. - :::tip +:::tip - The Tag Match option reduces the number of policies as you can create a single Policy that would grant access to all users or analysis that match the same tag keys. +The **Tag Match** option reduces the number of policies you need to create, as you can create a single Policy that would grant access to all users or analysis that match the same tag keys. - ::: +::: 4. **ANY** – all will be automatically included. diff --git a/docs/tagoio/tagorun/access-management/index.md b/docs/tagoio/tagorun/access-management/index.md index 4f231f72..661a730f 100644 --- a/docs/tagoio/tagorun/access-management/index.md +++ b/docs/tagoio/tagorun/access-management/index.md @@ -4,9 +4,9 @@ description: "This article explains how Access Management (AM) in TagoIO lets yo tags: ["tagoio"] sidebar_position: 1 --- -Access Management (AM) lets you securely grant access to specific resources in your TagoIO account. You create [Targets](/docs/tagoio/tagorun/access-management/defining-targets.md) (users or things) and assign [Permissions](/docs/tagoio/tagorun/access-management/defining-permissions.md) that determine which resources those Targets can access. +Access Management (AM) lets you securely grant access to specific resources in your TagoIO account. You create [Targets](/docs/tagoio/tagorun/access-management/defining-targets.md) (Users or Analysis) and assign [Permissions](/docs/tagoio/tagorun/access-management/defining-permissions.md) that determine which resources those Targets can access. -![Access Management interface example](/docs_imagem/tagoio/access-management-2.png) +![Access Management interface example](/docs_imagem/tagoio/rounded-image-1764600146285.png) ## Examples @@ -24,4 +24,7 @@ Some examples of how AM can be used: 4. Allow an Analysis to do a bulk device upload. Example: An Analysis with the tag `script = device_upload`, and the `Permission = device` with rules `Create` and with field `Any`. -*By using the option `Any` in the matching fields, you expose all that resource without restrictions.* +5. Allow an Analysis to get data from specific devices. + Example: An Analysis with the tag `script = device_upload`, and the `Permission = device` with rules `Read` and with field `Tag` and the tag key `device_id` and the tag value `1234567890`. + +*By using the option `Any` in the matching fields, you expose all of that resource without restrictions.* diff --git a/docs/tagoio/tagorun/dictionaries/import-export-for-dictionary.md b/docs/tagoio/tagorun/dictionaries/import-export-for-dictionary.md index 7dc78fb3..c9c61e9f 100644 --- a/docs/tagoio/tagorun/dictionaries/import-export-for-dictionary.md +++ b/docs/tagoio/tagorun/dictionaries/import-export-for-dictionary.md @@ -11,7 +11,7 @@ All data in a Dictionary can be exported into a CSV or JSON file. Exported files - Sending for translation to another language by keeping the keys and editing only the values - Keeping a backup to revert any changes to a known state -![Dictionary Pairs menu showing Import/Export options and sample downloads](/docs_imagem/tagoio/import-export-for-dictionary-2.png) +![Dictionary Pairs menu showing Import/Export options and sample downloads](/docs_imagem/tagoio/rounded-image-1761160129581.png) :::info @@ -31,7 +31,7 @@ The import and export functionality is available for users in the Scale plan. ## Behavior when adding new keys - When you add new keys to a language via import, the Dictionary will also add those keys with empty values to all other languages in the Dictionary. -## Samples +## CSV & JSON Samples TagoIO provides sample CSV and JSON files accessible from the Import and Export buttons for convenience and reference. In the Dictionary UI the menu includes options such as: - Import CSV - Import JSON diff --git a/docs/tagoio/tagorun/dictionaries/using-dictionaries-multi-language.md b/docs/tagoio/tagorun/dictionaries/using-dictionaries-multi-language.md index d70890ed..62698234 100644 --- a/docs/tagoio/tagorun/dictionaries/using-dictionaries-multi-language.md +++ b/docs/tagoio/tagorun/dictionaries/using-dictionaries-multi-language.md @@ -29,8 +29,8 @@ An auto‑complete feature is available to find Slugs and Keys as shown below. ## How to use dictionary keys ### 1) Create a Dictionary -First, create the Dictionary by clicking on the **[Dictionaries & Multi-language]** option from the top‑right menu in your Admin. -You will be asked to select a language that will be the first one made available; you may edit or add more languages later. A Slug is automatically created with the dictionary and can be edited afterwards. +First, create the Dictionary by clicking on the Dictionaries button in the sidebar menu in your Admin. +You will be asked to select a language that will be the first one made available; you may edit or add more languages later. You will also need to create a Slug for the dictionary which can also be edited later. Populate the dictionary with Key & Value pairs for substitution, then save it. Example for English: diff --git a/docs/tagoio/tagorun/getting-started/language-preferences.md b/docs/tagoio/tagorun/getting-started/language-preferences.md index b3058034..eb5d9db6 100644 --- a/docs/tagoio/tagorun/getting-started/language-preferences.md +++ b/docs/tagoio/tagorun/getting-started/language-preferences.md @@ -19,7 +19,6 @@ Some of the most commonly used languages for RUN applications include: ## How end-users choose a language All end-users can select their preferred language from the "Visualization Preferences" tab on the Account Setting page. - :::info Make sure that your current plan allows the deployment of multi-language for your end-users. See [pricing page](https://tago.io/pricing) diff --git a/docs/tagoio/tagorun/getting-started/signup-fields.md b/docs/tagoio/tagorun/getting-started/signup-fields.md index df12fa79..f83399f5 100644 --- a/docs/tagoio/tagorun/getting-started/signup-fields.md +++ b/docs/tagoio/tagorun/getting-started/signup-fields.md @@ -9,8 +9,8 @@ Mapping summary: | Signup field | Tag created for the User | |------------------|--------------------------| -| Field name | ---> Tag key | -| Input from user | ---> Tag value | +| Field name | Tag key | +| Input from user | Tag value | ## Customization diff --git a/docs/tagoio/tagorun/getting-started/user-engagement.md b/docs/tagoio/tagorun/getting-started/user-engagement.md index b1ff5382..98ffa832 100644 --- a/docs/tagoio/tagorun/getting-started/user-engagement.md +++ b/docs/tagoio/tagorun/getting-started/user-engagement.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- You can use third-party analytics and engagement tools to track and interact with your RUN users. The Integration module in the RUN session enables easy setup with popular solutions such as [Google Analytics](/docs/tagoio/tagorun/integrations/google-analytics.md) and [Zoho SalesIQ](/docs/tagoio/tagorun/integrations/zoho-salesiq.md). -![TagoRUN integrations screenshot](/docs_imagem/tagoio/user-engagement-2.png) +![TagoRUN integrations screenshot](/docs_imagem/tagoio/rounded-image-1767013456603.png) Some tools provide more than analytics and insights — they can add chat, bots, calls, remote screen access, and other engagement features to your RUN application. diff --git a/docs/tagoio/tagorun/getting-started/user-management.md b/docs/tagoio/tagorun/getting-started/user-management.md index 9767771d..ce36bfb5 100644 --- a/docs/tagoio/tagorun/getting-started/user-management.md +++ b/docs/tagoio/tagorun/getting-started/user-management.md @@ -3,9 +3,9 @@ title: "User Management" description: "This article explains how to view and manage users who sign up for your TagoIO application using the User Management module, including how tags are applied to users and how user fields can be used in Targets. It also notes how dashboard data access with TagoRUN affects Data Output quotas." tags: ["tagoio"] --- -You can visualize and control all users that sign up in your application under the User Management module (see the User Management documentation for details). +You can view and control all users that sign up in your application under the User Management module. -![User Management screen](/docs_imagem/tagoio/user-management-2.png) +![User Management screen](/docs_imagem/tagoio/rounded-image-1761309633786.png) ## Overview When you create and deploy your solution using TagoRun, all users that sign up will be listed in the [User Management](https://admin.tago.io/usermanagement) area. From there you can: diff --git a/docs/tagoio/tagorun/integrations/google-analytics.md b/docs/tagoio/tagorun/integrations/google-analytics.md index 70e2b51f..23754736 100644 --- a/docs/tagoio/tagorun/integrations/google-analytics.md +++ b/docs/tagoio/tagorun/integrations/google-analytics.md @@ -5,6 +5,8 @@ tags: ["tagoio"] --- You can integrate your RUN application with Google Analytics to track users and obtain actionable insights. Google Analytics lets you analyze in-depth details about your RUN users and provides data to help improve your solution.The tool can provide valuable insights to help you improve your solution based on real data. +![Google Analytics integration](/docs_imagem/tagoio/rounded-image-1764602658282.png) + All you need from Google Analytics is the [Measurement ID](https://support.google.com/analytics/answer/12270356?hl=en#:~:text=A%20Measurement%20ID%20is%20an,same%20as%20your%20destination%20ID) to add to your RUN setup. ## How to integrate Google Analytics with TagoIO @@ -17,7 +19,7 @@ To integrate, follow these steps: 3. Copy the Measurement ID from the web stream details in Google Analytics. -4. Back to TagoIO, go to your [RUN setup page](https://admin.tago.io/run), under **Session Integration > User Engagement**, paste the key into the *Google Analytics ID* field and save. +4. Back to TagoIO, go to your [RUN setup page](https://admin.tago.io/run), under **Integrations > User Engagement**, paste the key into the *Google Analytics ID* field and save. You are ready to track the visitors (your RUN users) using Google Analytics! diff --git a/docs/tagoio/tagorun/integrations/zoho-salesiq.md b/docs/tagoio/tagorun/integrations/zoho-salesiq.md index 734c329a..ebc6f087 100644 --- a/docs/tagoio/tagorun/integrations/zoho-salesiq.md +++ b/docs/tagoio/tagorun/integrations/zoho-salesiq.md @@ -11,14 +11,13 @@ You can easily integrate your RUN application with Zoho SalesIQ to track and eng 2. Copy the key (only the key value shown after `widgetcode:` in the SalesIQ script). - ![SalesIQ widget setup screenshot](/docs_imagem/tagoio/zoho-salesiq-2.png) 3. Enable Visitor Tracking for your RUN URL. -4. Then, back to TagoIO, in your [RUN](https://admin.tago.io/run) setup page, under the session Integration> User Engagement, paste the key in the Zoho ID field. +4. Then, back to TagoIO, in your [RUN](https://admin.tago.io/run) setup page, under **Integrations > User Engagement**, paste the key in the Zoho ID field. -You are now ready to track visitors (your RUN users) using SalesIQ! +You are now ready to track your RUN users using SalesIQ! You will be able to know who is accessing your RUN, when, for how long, and what type of browser and devices were used. Also, you can enable Chat, Bots, remote screen access, analytics, and add functions to comply with GDPR (cookies disclaimer). diff --git a/docs/tagoio/tagorun/single-sign-on-sso.md b/docs/tagoio/tagorun/single-sign-on-sso.md index 2f4be8e1..4cf22bf4 100644 --- a/docs/tagoio/tagorun/single-sign-on-sso.md +++ b/docs/tagoio/tagorun/single-sign-on-sso.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- By using Single Sign-On (SSO) integration, end users can sign in to a RUN application using credentials from your trusted user database provided by third‑party identity services. Supported providers include Okta, Auth0, Microsoft Azure AD, OneLogin, PingIdentity, Google Workspace, and others. -![TagoIO SSO integrated with 3rd-party services](/docs_imagem/tagoio/single-sign-on-sso-2.png) +![TagoIO SSO integrated with 3rd-party services](/docs_imagem/tagoio/rounded-image-1764611428517.png) ## Overview Single Sign-On (SSO) allows RUN applications to delegate authentication to an external identity provider (IdP). This enables centralized user management, single credential use across multiple services, and simplified user access to RUN and other connected services. diff --git a/docs/tagoio/tutorials/abs-telemetry.md b/docs/tagoio/tutorials/abs-telemetry.md index 24385744..9f16f444 100644 --- a/docs/tagoio/tutorials/abs-telemetry.md +++ b/docs/tagoio/tutorials/abs-telemetry.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- Devices from ABS Telemetry can be easily integrated with TagoIO. The integration allows uplink communication between the device and TagoIO while parsing messages to extract commands and variables in real time. -![ABS Telemetry device integration diagram (device → cellular network → TagoIO)](/docs_imagem/tagoio/abs-telemetry-2.png) +![ABS Telemetry device integration diagram (device → cellular network → TagoIO)](/docs_imagem/tagoio/rounded-image-1761311582465.png) You will need to set up your device using the ABS portal and your TagoIO account. @@ -38,12 +38,12 @@ Learn more information about the [ABS devices configuration](http://www.abstelem Add a **[device](https://tago.io/devices)** in your account at TagoIO. Go to *Devices* and click on **'Add Devices'**, filter network by **'Cellular'** and pick your device from the list. -![Image 2](/docs_imagem/tagoio/Screen-20Shot-202019-10-28-20at-2016.41.44-bjQ.png) +![Image 2](/docs_imagem/tagoio/rounded-image-1761311651518.png) > Currently, the following device is integrated with TagoIO: **ABS CEL IO** Click on **'Create Device'**, and you will have confirmation that the device was created. -Turn your device on, and wait for the data to arrive and hit your data **[bucket](/docs/tagoio/devices/)**, and it will be ready to be shown in the dashboards. You can start to build your **[Dashboard](/docs/tagoio/dashboards/)** by adding gauges, tables and more. +Turn your device on, and wait for the data to arrive and be stored in your **[device](/docs/tagoio/devices/)**; it will be ready to be shown in the dashboards. You can start to build your **[Dashboard](/docs/tagoio/dashboards/)** by adding graphs, tables and more. Enjoy your ABS devices with TagoIO! diff --git a/docs/tagoio/tutorials/adeunis-with-lorawan.md b/docs/tagoio/tutorials/adeunis-with-lorawan.md index 0c7f0a49..1505a2e2 100644 --- a/docs/tagoio/tutorials/adeunis-with-lorawan.md +++ b/docs/tagoio/tutorials/adeunis-with-lorawan.md @@ -49,9 +49,9 @@ Each provider link points to the corresponding TagoIO tutorial for configuring Adeunis devices with that network. After you have completed the setup above, you will be ready to move forward.\ -Now, just turn your Adeunis device on and wait for the data to hit your **data -bucket**. Every time the device sends data, the parser will be executed, the -extracted data sent to the bucket, and it will be ready to be shown in the +Now, just turn your Adeunis device on and wait for the data to be stored on your **device**.\ +Every time the device sends data, the parser will be executed, the +extracted data will be stored in the device, and it will be ready to be shown in dashboards. You can start building your [dashboards](/docs/tagoio/dashboards/) immediately.\ diff --git a/docs/tagoio/tutorials/adeunis-with-sigfox.md b/docs/tagoio/tutorials/adeunis-with-sigfox.md index d9eb0f3a..92edbe69 100644 --- a/docs/tagoio/tutorials/adeunis-with-sigfox.md +++ b/docs/tagoio/tutorials/adeunis-with-sigfox.md @@ -9,7 +9,7 @@ backend. Incoming messages from Adeunis devices are parsed in real time so measured variables are extracted and made available to TagoIO for display in widgets and for processing. -![Adeunis + Sigfox + TagoIO diagram](/docs_imagem/tagoio/adeunis-with-sigfox-2.png) +![Adeunis + Sigfox + TagoIO diagram](/docs_imagem/tagoio/rounded-image-1761311243395.png) All data sent by your device will be readily available to be displayed in widgets and processed in your [Analysis](/docs/tagoio/analysis/). @@ -26,12 +26,10 @@ Parser". To add an Adeunis device in TagoIO: 1. Go to [Devices](https://tago.io/devices). -2. Click on "Add Devices". +2. Click on "+ New Device". 3. Filter the list by network and select "Sigfox". 4. Pick your specific Adeunis device from the list. -![Select the device type screen in TagoIO](/docs_imagem/tagoio/adeunis-with-sigfox-2.png) - ### Integrate your Adeunis with TagoIO 1. Turn on your Adeunis device and wait for the data to reach your bucket. diff --git a/docs/tagoio/tutorials/beagle-bone-black.md b/docs/tagoio/tutorials/beagle-bone-black.md index a9538f95..c707541c 100644 --- a/docs/tagoio/tutorials/beagle-bone-black.md +++ b/docs/tagoio/tutorials/beagle-bone-black.md @@ -3,7 +3,7 @@ title: "Beagle Bone Black" description: "This short tutorial explains how to integrate a BeagleBone Black (BBB) board with TagoIO, demonstrating how to send a digital input status to a dashboard and configure an Action to email when the switch closes." tags: ["tagoio"] --- -![BeagleBone Black board](/docs_imagem/tagoio/beagle-bone-black-2.jpg) +![BeagleBone Black board](/docs_imagem/tagoio/rounded-image-1761311943540.png) ## Overview This simple tutorial uses the BeagleBone Black (BBB) board to demonstrate key principles for integrating your solution with TagoIO. Beyond connecting the BBB to the cloud, you will learn how to structure and reuse this code in your own application. @@ -13,13 +13,13 @@ The circuit is straightforward: a single digital input is connected to a normall ### Adding the Device 1. Log in to your TagoIO account and navigate to the **[Devices](https://tago.io/devices)** section. 2. Click the blue **Add Device** button, give it the name `dev01`, and click **Save**. -3. All devices must use a valid token when accessing Tago. The token is automatically generated upon creation. Open the device’s **General information** page, click **QR Code** or **Tokens**, and copy the token to insert into your BBB code later. +3. All devices must use a valid token when accessing TagoIO. The token is automatically generated upon creation. Open the device's **General information** page, click **QR Code** or **Tokens**, and copy the token to insert into your BBB code later. ### Building the Dashboard 1. In the left sidebar, open **Dashboards** and click the plus icon (`+`). 2. Name the dashboard (e.g., `BBB Dashboard`) and click **Save**. 3. Add a widget: click the top‑right plus icon, choose **Display**, and configure it to show the variable `switch`. -4. Select your bucket (`dev01`), device (`dev01`), and click **Select as new option** then **Save**. +4. Select your device (`dev01`), and click **Select as new option** then **Save**. 5. The widget will update in real time once data starts flowing from the BBB. ### Sending e‑mail Action @@ -92,7 +92,7 @@ while True: ``` #### Tips for your code -1. Import the Tago library: `from tago import Tago`. +1. Import the TagoIO library: `from tago import Tago`. 2. Replace `MY_DEVICE_TOKEN` with the token created for your device. 3. Prepare a JSON payload, e.g., `data_to_insert = {'variable': 'switch', 'value': 'closed'}`. 4. Send data: `result = my_device.insert(data_to_insert)`. diff --git a/docs/tagoio/tutorials/connecting-zen15-power-using-smartthings-hub.md b/docs/tagoio/tutorials/connecting-zen15-power-using-smartthings-hub.md index 30fd7067..8136b71b 100644 --- a/docs/tagoio/tutorials/connecting-zen15-power-using-smartthings-hub.md +++ b/docs/tagoio/tutorials/connecting-zen15-power-using-smartthings-hub.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- This tutorial shows how to bring electric power and energy measurements from the Zen15 sensor into your TagoIO account using a Samsung SmartThings hub. -![SmartThings Hub from Samsung](/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-2.png) +![SmartThings Hub from Samsung](/docs_imagem/tagoio/rounded-image-1761312069480.png) The Zooz [Zen15](https://www.getzooz.com/zen15-power-switch/) Power Switch connects to the SmartThings hub using Z‑Wave wireless technology. The Zen15 can control loads and measure power and energy in real time so data can be displayed and processed by TagoIO. diff --git a/docs/tagoio/tutorials/markdown-guide.md b/docs/tagoio/tutorials/markdown-guide.md index a6f3066f..2a4f5a56 100644 --- a/docs/tagoio/tutorials/markdown-guide.md +++ b/docs/tagoio/tutorials/markdown-guide.md @@ -65,7 +65,7 @@ Block quote example: ## Images -Need to upload an image? [TagoIO Files](/docs/tagoio/files) has a great interface. +Need to upload an image? [TagoIO Files](/docs/tagoio/files) can help you with that. Example Markdown for an image: @@ -73,10 +73,6 @@ Example Markdown for an image: ![Alt text](path/to/image.jpg) ``` -Rendered example image placeholder: - - - ## Tables Basic Markdown table example: diff --git a/docs/tagoio/tutorials/mqtt-with-sensor-tag.md b/docs/tagoio/tutorials/mqtt-with-sensor-tag.md index de67cf7f..03215c29 100644 --- a/docs/tagoio/tutorials/mqtt-with-sensor-tag.md +++ b/docs/tagoio/tutorials/mqtt-with-sensor-tag.md @@ -3,19 +3,19 @@ title: "MQTT with Sensor Tag" description: "This article explains how to use the Texas Instruments SensorTag (CC2650) to send sensor data to TagoIO via MQTT, including connectivity flow and the sensors available on the device." tags: ["tagoio"] --- -This example shows how to use the SensorTag Bluetooth module (Texas Instruments CC2650) to send data to TagoIO. No code modification is required on the SensorTag itself; because the SensorTag is used with MQTT, only a configuration setup is necessary. +This example shows how to use the SensorTag Bluetooth module (Texas Instruments CC2650) to send data to TagoIO. No code modification is required on the SensorTag itself; because the SensorTag is used with MQTT, only the configuration setup is necessary. The SensorTag communicates with a mobile device over Bluetooth. Texas Instruments provides a mobile app that converts that Bluetooth communication into MQTT and forwards the data to the cloud over cellular or Wi‑Fi. ## Connectivity Diagram -![SensorTag to TagoIO flow diagram](/docs_imagem/tagoio/mqtt-with-sensor-tag-2.png) +![SensorTag to TagoIO flow diagram](/docs_imagem/tagoio/rounded-image-1761312428484.png) ## Learn more Learn more about the SensorTag CC2650 and how to get started: [SensorTag CC2650 and how to get started](https://www.ti.com/tool/CC2650STK) ## What this example does - All sensor data from the SensorTag will be posted to TagoIO. -- Sensor data can be visualized on a TagoIO dashboard in real time: [dashboard](/docs/tagoio/dashboards/). +- Sensor data can be visualized on a TagoIO [dashboard](/docs/tagoio/dashboards/) in real time. - This example uses the hardware version tested by the authors. ## Sensors included @@ -64,7 +64,7 @@ The tested SensorTag hardware contains the following 10 sensors: ### Creating an MQTT Action to save data 1. Go to **Actions** and click **Create new**. 2. Set the trigger type to **MQTT Topic**. -3. Choose the action type **Insert data to device bucket**. +3. Choose the action type **Insert data into device**. 4. Select your SensorTag device, set the topic to `data`, and save the action. Once the action is in place, all incoming MQTT messages on the `data` topic will be stored in the device’s bucket for further analysis or visualization. \ No newline at end of file diff --git a/docs/tagoio/tutorials/queclink-gps.md b/docs/tagoio/tutorials/queclink-gps.md index 2a7a3cda..86556600 100644 --- a/docs/tagoio/tutorials/queclink-gps.md +++ b/docs/tagoio/tutorials/queclink-gps.md @@ -5,7 +5,7 @@ tags: ["tagoio"] --- Queclink GPS can be integrated with TagoIO through middleware that translates the device's TCP/IP protocol. The middleware enables uplink communication between the device and TagoIO while parsing messages to extract commands and variables in real time. -![Queclink device, Cellular Network, and TagoIO flow diagram](/docs_imagem/tagoio/queclink-gps-2.png) +![Queclink device, Cellular Network, and TagoIO flow diagram](/docs_imagem/tagoio/rounded-image-1761312647438.png) > Downlink messages must be accomplished using SMS messages or Queclink tools; they cannot be sent from TagoIO. @@ -34,13 +34,11 @@ Add a device in your account at TagoIO. Go to [Devices](https://admin.tago.io/de - GV55* *contact us for updates* -Once the device is created, you will receive a confirmation. Turn your GPS on and wait for data to arrive in your bucket: [Buckets](/docs/tagoio/devices/). The data will be ready to display in dashboards. +Once the device is created, you will receive a confirmation. Turn your GPS on and wait for data to be stored on your [Device](/docs/tagoio/devices/). ### Building Dashboards -Create a dashboard by adding gauges, maps (add the variable **'location'**), tables, and more. For example: - - +Create a dashboard by adding gauges, maps (add the variable **'location'**), tables, and more. You can also set up notifications to send push notifications, SMS, or emails: [Notifications](/docs/tagoio/getting-started/notification.md). Advanced analysis scripts are available here: [Scripts](/docs/tagoio/analysis/creating-analysis.md). diff --git a/docs/tagoio/tutorials/radiobridge-devices.md b/docs/tagoio/tutorials/radiobridge-devices.md index 2e464258..e2b76785 100644 --- a/docs/tagoio/tutorials/radiobridge-devices.md +++ b/docs/tagoio/tutorials/radiobridge-devices.md @@ -5,23 +5,24 @@ tags: ["tagoio", "devices"] --- TagoIO is fully integrated with RadioBridge devices connected over Sigfox or -LoRaWAN, providing seamless integration with the RadioBridge backend. +LoRaWAN, providing seamless integration with the RadioBridge backend. Read more about [Radio Bridge](https://radiobridge.com/). -![Diagram of devices, network, RadioBridge server, and TagoIO with uplink/downlink arrows](/docs_imagem/tagoio/radiobridge-devices-2.png) - -Read more about [Radio Bridge](https://radiobridge.com/). +![Diagram of devices, network, RadioBridge server, and TagoIO with uplink/downlink arrows](/docs_imagem/tagoio/rounded-image-1761312825480.png) All data sent by your device will be readily available to display in widgets or to be processed by your Analysis. +:::info You can perform both uplink and downlink operations. +::: ## Step 1: -First go to your TagoIO account, and if this is your first device connected +First, go to your TagoIO account, and if this is your first device connected between Radio Bridge and TagoIO, you will need to create an -[Authorization](/docs/tagoio/integrations/general/authorization.md).\ -Copy the Authorization by clicking in the COPY button to use in the next step. +[Authorization](/docs/tagoio/integrations/general/authorization.md). + +Copy the **Authorization** to use in the next step. ### Step 2: @@ -34,8 +35,6 @@ TagoIO callback URL and set an Authorization Header of your choice. [https://radiobridge.middleware.tago.io/uplink](https://radiobridge.middleware.tago.io/uplink) - **Header Authorization Code:** Enter the one you generated at Step 1. -Copy the Unique API URL for the next step and press Update. - ### Step 3: Copy the **Unique API URL** and return to the TagoIO Authorization page by @@ -54,9 +53,8 @@ Then follow the directions to integrate your device with TagoIO and start building your own application.\ When completed, click on **Create Device**. -Turn your Radio Bridge device on, and wait for the data to arrive in your -bucket. Every time the device sends data it will be available in the bucket and -shown in the dashboard: [bucket](/docs/tagoio/devices/).\ +Turn your Radio Bridge device on, and wait for the data to be stored on your +device. Every time the [device](/docs/tagoio/devices/) sends data, it will be stored in the device's data and be ready to be shown in the dashboard.\ You can start editing the installed dashboard. Also, you can create diff --git a/docs/tagoio/tutorials/raspberry-pi.md b/docs/tagoio/tutorials/raspberry-pi.md index 2126679a..61e2b08c 100644 --- a/docs/tagoio/tutorials/raspberry-pi.md +++ b/docs/tagoio/tutorials/raspberry-pi.md @@ -3,7 +3,7 @@ title: "Raspberry Pi" description: "A brief guide pointing to a community tutorial showing how to connect a Raspberry Pi to TagoIO using the TagoIO SDK or the MQTT protocol; also directs readers to additional tutorials in the TagoIO Community forum." tags: ["tagoio"] --- -![Raspberry Pi board](/docs_imagem/tagoio/raspberry-pi-2.png) +![Raspberry Pi board](/docs_imagem/tagoio/rounded-image-1761313093242.png) Visit this [tutorial (Community)](https://community.tago.io/t/raspberry-pi-tagoio-using-sdk-or-mqtt-getting-started/991) to learn how to communicate a Raspberry Pi board with TagoIO using the TagoIO SDK or the MQTT protocol. diff --git a/docs/tagoio/tutorials/sensit-with-sigfox.md b/docs/tagoio/tutorials/sensit-with-sigfox.md index 45579b53..96b9a54b 100644 --- a/docs/tagoio/tutorials/sensit-with-sigfox.md +++ b/docs/tagoio/tutorials/sensit-with-sigfox.md @@ -9,7 +9,7 @@ the Sigfox backend and parses incoming messages to extract measured variables in real time. All data sent by your device will be available to display in widgets or to process in your Analysis. -![Sens'it + Sigfox + TagoIO Connectivity Diagram](/docs_imagem/tagoio/sensit-with-sigfox-2.png) +![Sens'it + Sigfox + TagoIO Connectivity Diagram](/docs_imagem/tagoio/rounded-image-1761313210646.png) Sens'it + Sigfox + TagoIO Connectivity Diagram @@ -30,29 +30,23 @@ Sens'it + Sigfox + TagoIO Connectivity Diagram ## Add the device to TagoIO -1. In TagoIO, go to Devices (see [Devices](/docs/tagoio/devices/) for the - Devices section). -2. Click on "Add Devices". +1. In TagoIO, go to [Devices](https://admin.tago.io/devices). +2. Click on "+ New Device". 3. Filter the network by "Sigfox" and choose your Sens'it device from the list (select v2 or v3 accordingly). 4. After adding the device, incoming data will be parsed by TagoIO and become available for widgets and Analysis. -![TagoIO — Select the device type](/docs_imagem/tagoio/sensit-with-sigfox-2.png) - -TagoIO — Select the device type (use the network filter to find Sigfox devices) - ## Dashboard Setup After adding the device, click on the newly created dashboard in the left menu and associate it with your Sens'it device. Turn the device on; data will arrive automatically into the bucket and be displayed in widgets. -## Data Buckets +## Data Storage Every time the device sends data, the parser is executed, the extracted data is -sent to a bucket, and it becomes ready for display in dashboards or further -analysis. +sent to the device's data, and it will be ready to be displayed in dashboards or processed in [Analysis](/docs/tagoio/analysis/). ## Custom Parsing (v2) diff --git a/docs/tagoio/tutorials/thinxtra-xkit-for-sigfox.md b/docs/tagoio/tutorials/thinxtra-xkit-for-sigfox.md deleted file mode 100644 index 14b775b1..00000000 --- a/docs/tagoio/tutorials/thinxtra-xkit-for-sigfox.md +++ /dev/null @@ -1,94 +0,0 @@ ---- -title: "Thinxtra Xkit for Sigfox" -description: "This article explains how to connect the Thinxtra Xkit Sigfox board to TagoIO and other platforms, and provides a diagram of the Xkit board pinout for reference." -tags: ["tagoio"] ---- - -This tutorial explains how to connect the Xkit from Thinxtra with TagoIO. The -Sigfox board can be connected to a PC, Mac, Arduino, Raspberry Pi, and other -platforms. - -![Thinxtra Xkit board](/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png) - -Here is a diagram of the Xkit board's pinout. For more details, click -[here](https://www.thinxtra.com/xkit/). - -## Pinout Diagram - -![Thinxtra Xkit pin-out configuration](/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png) - -(Note: The image above shows the Thinxtra Xkit pin‑out configuration including a -color legend for pins linked to Power, Sensors, and Module.) - -## Xkit Board - -![Xkit board](/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png) - -## Pinout Diagram (Alternate View) - -![Xkit pin‑out diagram](/docs_imagem/tagoio/xkit_pinout-Sgw.png) - -## Payload Example - -Xkit can be programmed with a file that will send data from the sensors with a -payload format as shown below. TagoIO is flexible enough to parse this payload -in order to extract the variables – it is done through a script coded in the -[Payload Parser](/docs/tagocore/resources/device/payload-parser.md). - -![Payload example](/docs_imagem/tagoio/paylot_xkit-i8s.png) - -> Calculations to extract temperature, pressure, photo, acceleration are done by -> the parser script. - -## Setup Steps - -### 1. Xkit Setup - -Follow the installation guide from [Thinxtra](https://www.thinxtra.com/xkit/) -and prepare your Xkit to send data to the -[Sigfox network](/docs/tagoio/integrations/networks/sigfox/sigfox.md). - -### 2. TagoIO and Sigfox Setup - -Go to **[Devices](https://admin.tago.io/devices)**, click on _Add Devices_, and -filter network by Sigfox to search for Thinxtra. - -![Device selection](/docs_imagem/tagoio/thinxtra_selection_tagoio-PIU.png) - -Then, just follow the directions to integrate your Xkit with TagoIO and start -building your own application in minutes. - -> If you have questions about how to configure your account for Sigfox and -> TagoIO, read the article -> [Sigfox](/docs/tagoio/integrations/networks/sigfox/sigfox.md). - -Now, click on the new dashboard created (left menu), and associate it with the -device that you just added. - -> Check with your Xkit distributor about how to register the Xkit in the Sigfox -> Portal. - -Now, just turn your Xkit board on, and wait for the data to hit your data -bucket. Every time the Xkit sends data, an action will be triggered and the -script will parse the data sending it to the bucket, ready to be displayed by -the widgets. - -You can start editing your dashboard as needed. - -![Dashboard](/docs_imagem/tagoio/thinxtra_Dash-7pM.png) - -:::info - -You can edit the [parse script](/docs/tagocore/resources/device/payload-parser.md) created -for your device that extracts variables from the payload. - -::: - -Also, you can create -[notifications](/docs/tagoio/getting-started/notification.md) and more advanced -[scripts](/docs/tagoio/analysis/creating-analysis.md) as needed. - -Learn more about -[Downlink for Sigfox](/docs/tagoio/integrations/networks/sigfox/sigfox-downlink.md). - -Enjoy your Thinxtra Xkit with Tago! diff --git a/docs/tagoio/tutorials/touchtag-lorawan-everynet.md b/docs/tagoio/tutorials/touchtag-lorawan-everynet.md index 2994f161..da2c8ae7 100644 --- a/docs/tagoio/tutorials/touchtag-lorawan-everynet.md +++ b/docs/tagoio/tutorials/touchtag-lorawan-everynet.md @@ -9,21 +9,19 @@ TagoIO integrates with TouchTAG devices through a complete connector to the Ever TouchTAG is a disposable, action-driven IoT device — a very low-cost, compact, and lightweight geotag with additional sensor functionality. -![TouchTAG — Everynet integration diagram](/docs_imagem/tagoio/touchtag-lorawan-everynet-2.png) +![TouchTAG — Everynet integration diagram](/docs_imagem/tagoio/rounded-image-1769104184640.png) ## Add a TouchTAG device to TagoIO To add your TouchTAG device to TagoIO: 1. Go to the [Devices](/docs/tagoio/devices/) section in TagoIO. -2. Click on "Add Devices". +2. Click on "+ New Device". 3. Select the connector "LoRaWAN Everynet" (select the LoRaWAN Everynet connector). 4. Search for "TouchTag" and create the device. After creating the device, generate an **Authorization** for it (one per application). [Generate Authorization](/docs/tagoio/integrations/general/authorization.md) -![Connector selection and device search in TagoIO](/docs_imagem/tagoio/touchtag-lorawan-everynet-2.png) - ## Notes - The connector handles decryption and parsing of the TouchTAG payloads so measured variables are available in real time in TagoIO. @@ -33,8 +31,6 @@ To add your TouchTAG device to TagoIO: - Turn your TouchTAG device on and wait for data to arrive. Each time the device sends data, the parser is executed, extracted data is sent to the bucket, and it becomes available in dashboards. - You can create **notifications** and more advanced **scripts** as needed. -![TouchTag Dashboard](/docs_imagem/tagoio/TouchTag_Dashboard_Tago-0VU.png) - ## References - Refer to the [Devices](/docs/tagoio/devices/) documentation for general instructions on creating and managing devices in TagoIO. diff --git a/docs/tagoio/widgets/custom-widget/echarts-custom-widget-tutorial-.md b/docs/tagoio/widgets/custom-widget/echarts-custom-widget-tutorial-.md index a3d3b229..986bbe98 100644 --- a/docs/tagoio/widgets/custom-widget/echarts-custom-widget-tutorial-.md +++ b/docs/tagoio/widgets/custom-widget/echarts-custom-widget-tutorial-.md @@ -7,7 +7,7 @@ In this tutorial, we will guide you through creating a Ring Gauge custom widget To achieve this, we leverage the [ECharts library](https://echarts.apache.org/), a robust and highly customizable charting library that simplifies the development of interactive and visually appealing data visualizations. Using ECharts can significantly speed up development and help ensure the custom widget is both efficient and aesthetically pleasing. - +![Ring Gauge custom widget](/docs_imagem/tagoio/rounded-image-1761311392776.png) This tutorial is structured into three comprehensive sections to facilitate a smooth learning experience: diff --git a/docs/tagoio/widgets/displays/card-widget.md b/docs/tagoio/widgets/displays/card-widget.md index 91fc1304..45feb3bb 100644 --- a/docs/tagoio/widgets/displays/card-widget.md +++ b/docs/tagoio/widgets/displays/card-widget.md @@ -7,7 +7,7 @@ Use Card to display the last value of a variable, its unit, and a mini‑chart. ![Three Card widget examples showing value, unit, and mini-chart](/docs_imagem/tagoio/card-widget-2.gif) -This widget also accepts features like metadata (see the Metadata documentation), which can be set in your variable data. +This widget also accepts features like [metadata](/docs/tagoio/devices/payload-parser/metadata.md), which can be set in your variable data. ## Creating your own @@ -18,7 +18,7 @@ To add a Card to your dashboard, choose the Card widget from the widget list and This field allows you to set the device and variable that will be used in this widget. For **Normal dashboards** you select one device from your list of devices and then pick the variable that contains the data. -For **Blueprint dashboards** you add a Blueprint device (see [Blueprint devices](/docs/tagoio/devices/blueprint-devices-entities.md)) and input the name of the variable. +For **Blueprint dashboards** you add a [Blueprint device](/docs/tagoio/devices/blueprint-devices-entities.md) and add the name of the variable. When using a Blueprint dashboard, the Variable field will not list variables to be picked because it doesn't know the devices linked to your Blueprint Device. diff --git a/docs/tagoio/widgets/displays/display-widget.md b/docs/tagoio/widgets/displays/display-widget.md index 58de68aa..56ef656c 100644 --- a/docs/tagoio/widgets/displays/display-widget.md +++ b/docs/tagoio/widgets/displays/display-widget.md @@ -23,6 +23,6 @@ The *Data From* field allows you to specify which device or entity provides the - In a **Normal dashboard**, select one device or an entity from your list, then choose the variable that contains the data. - In a **Blueprint dashboard**, add a Blueprint Device or Entity and input the name of the variable that holds the information. Because a Blueprint dashboard does not know which devices are linked to it, the field will not list variables until you provide the device/entity. -After adding a variable, click the cog icon to edit specific options for that variable—such as formulas, color, and more. Click the close icon to remove the variable from the widget’s data. +After adding a variable, click the settings icon to edit specific options for that variable—such as formulas, color, and more. Click the close icon to remove the variable from the widget’s data. **Note:** The *Data From* field is dependent on the type of dashboard you are using; the differences are explained above. diff --git a/docs/tagoio/widgets/general/data-analytics.md b/docs/tagoio/widgets/general/data-analytics.md index 5b5e1451..063ebf17 100644 --- a/docs/tagoio/widgets/general/data-analytics.md +++ b/docs/tagoio/widgets/general/data-analytics.md @@ -13,7 +13,7 @@ Data Analytics is currently available for the widgets listed below, with support - [Horizontal Bar](/docs/tagoio/widgets/charts/horizontal-bar-widget.md) - [Vertical Column](/docs/tagoio/widgets/charts/vertical-column-widget.md) - [Multiple Charts](/docs/tagoio/widgets/charts/multiple-charts-widget.md) -- [Icon](/docs/tagoio/widgets/displays/icons-widget.md)md) +- [Icon](/docs/tagoio/widgets/displays/icons-widget.md) ## Available Functions diff --git a/docs/tagoio/widgets/index.md b/docs/tagoio/widgets/index.md index 4c4e3244..ecc7ae84 100644 --- a/docs/tagoio/widgets/index.md +++ b/docs/tagoio/widgets/index.md @@ -76,4 +76,4 @@ The following widgets are provided out of the box (icons and labels shown): ### Common Features -Check the Widgets > General documentations for commom features that can be used accross almost all widgets. +Check the Widgets > General documentations for common features that can be used across almost all widgets. diff --git a/docs/tagoio/widgets/input-widgets/input-form/field-types-for-input-form.md b/docs/tagoio/widgets/input-widgets/input-form/field-types-for-input-form.md index 23ef3c73..02d36ffa 100644 --- a/docs/tagoio/widgets/input-widgets/input-form/field-types-for-input-form.md +++ b/docs/tagoio/widgets/input-widgets/input-form/field-types-for-input-form.md @@ -87,7 +87,7 @@ You can customize the devices shown by the list through tags. Configuring tags w ## 7. Dropdown -It displays a dropdown menu with options that you define. The value of the field will be the selected options, and these options can be defined as static or dynamic with the dropdown being filled up with data coming from a variable. Learn more about **Creating Dynamic Dropdown selection using Forms.** +It displays a dropdown menu with options that you define. The value of the field will be the selected option, and these options can be defined as static or dynamic with the dropdown being populated with data coming from a variable. Learn more about **Creating Dynamic Dropdown selection using Forms.**
![Dropdown example](/docs_imagem/tagoio/field-types-for-input-form-8.gif) @@ -95,7 +95,7 @@ It displays a dropdown menu with options that you define. The value of the field ## 8. Dropdown Multiple -It displays a dropdown menu with options that you define. The value of the field will be the multiple options selected, and these options can be defined as static or dynamic with the dropdown being filled up with data coming from a variable. +It displays a dropdown menu with options that you define. The value of the field will be the multiple options selected, and these options can be defined as static or dynamic with the dropdown being populated with data coming from a variable.
![Dropdown multiple example](/docs_imagem/tagoio/field-types-for-input-form-9.gif) diff --git a/docs/tagoio/widgets/map-and-location/map-widget/router.md b/docs/tagoio/widgets/map-and-location/map-widget/router.md index bf76fe05..94231c0d 100644 --- a/docs/tagoio/widgets/map-and-location/map-widget/router.md +++ b/docs/tagoio/widgets/map-and-location/map-widget/router.md @@ -9,12 +9,10 @@ You can enable the Router option to allow users to get directions to a destinati ### How to configure the Router -To use the router enter the map widget in edit mode, navigate to - you must first define an **origin** point. +To use the router, enter the map widget in edit mode. You must first define an **origin** point. This is done by selecting a device and specifying the variable that holds its coordinates (for example, GPS data from the TagoIO mobile app or any other device that reports latitude/longitude). -![Router example showing origin and destination]( -) +![Router example showing origin and destination](https://cdn.elev.io/file/uploads/VkSrjeSoWpdg7LeGdh2jKUEagxh0dd_cO83j6HUV_6s/9z77pHL2QbGjjb7zC7zTBDddaFsnKAlzDLoOUHrvr88/router_example-5Vo.png) Once the origin is set, you can enable the router option in the map widget settings. The following screenshot shows how to activate it: diff --git a/docs/tagoio/widgets/tables/device-list-widget.md b/docs/tagoio/widgets/tables/device-list-widget.md index 0e4e7103..11e7bfd2 100644 --- a/docs/tagoio/widgets/tables/device-list-widget.md +++ b/docs/tagoio/widgets/tables/device-list-widget.md @@ -11,7 +11,7 @@ The Device List works as a dynamic table. You can customize its colors and colum ![Device List widget configuration and preview](/docs_imagem/tagoio/device-list-widget-2.png) ### 2. Device filtering -This option is required to be filled up in order to show your devices. You can either filter the devices that will show up in your list by the devices' tag key and tag value, or by tag match for one of the blueprint devices on your dashboard. +This option is required to be filled in order to show your devices. You can either filter the devices that will show up in your list by the devices' tag key and tag value, or by tag match for one of the blueprint devices on your dashboard. You can also have multiple filters working at the same time. It works as an AND operator, and the device must match all the filters. diff --git a/docs/tagoio/widgets/tables/user-list-widget.md b/docs/tagoio/widgets/tables/user-list-widget.md index f8273174..87558941 100644 --- a/docs/tagoio/widgets/tables/user-list-widget.md +++ b/docs/tagoio/widgets/tables/user-list-widget.md @@ -16,10 +16,10 @@ You can also adjust the table’s appearance by changing colors, font styles, an ## 2. User List filtering -This option is required to be filled up in order to show your users. You can filter which users appear in the list by: +This option is required to be filled in order to show your users. You can filter which users appear in the list by: - **Tag Key and Tag Value** – All users for the list must have the same tag key and tag value specified by you in this filter. -- **Blueprint Device Tags** – Select a blueprint device from the dashboard and one tag key. The user for the list must match the same value of that tag key in the selected blueprint device. +- **Blueprint Device Tags** – Select a blueprint device from the dashboard and one tag key. The users for the list must match the same value of that tag key in the selected blueprint device. You can also apply multiple filters simultaneously; note that this works as an AND operator, so the user must match *all* specified filters. diff --git a/src/css/custom.css b/src/css/custom.css index 91f02694..12516fbe 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -1008,6 +1008,29 @@ html[data-theme="dark"] .youtube-container { vertical-align: bottom; } +.rounded-image { + border-radius: 20px; + overflow: hidden; + border: 8px solid #CCCCCC; +} + +/* Automatically apply rounded-image styles to all GIF images */ +.gif-wrapper { + display: inline-block; + border-radius: 20px; + border: 8px solid #CCCCCC; + background-color: #CCCCCC; + overflow: hidden; + line-height: 0; +} + +.gif-wrapper .gif-image { + display: block; + clip-path: inset(2px); + max-width: 100%; + height: auto; +} + .mermaid { display: flex; align-items: center; diff --git a/src/theme/MDXComponents.tsx b/src/theme/MDXComponents.tsx index 69d6214f..bbeba995 100644 --- a/src/theme/MDXComponents.tsx +++ b/src/theme/MDXComponents.tsx @@ -13,9 +13,30 @@ const Mermaid = (props: React.ComponentProps) => ( ); +// Custom img component that wraps GIFs to apply border and clipping correctly +const Img = (props: React.ImgHTMLAttributes) => { + const { src, className, ...rest } = props; + // Check if src ends with .gif (case insensitive, ignoring query params) + const srcPath = src?.split("?")[0] || ""; + const isGif = srcPath.toLowerCase().endsWith(".gif"); + + if (isGif) { + return ( + + + + ); + } + + // For non-GIF images, use the original img component from MDXComponents + const OriginalImg = MDXComponents.img || "img"; + return ; +}; + export default { ...MDXComponents, YouTube, Mermaid, DocCardList, + img: Img, }; diff --git a/static/docs_imagem/tagoio/1563385125217-eok.png b/static/docs_imagem/tagoio/1563385125217-eok.png deleted file mode 100644 index 09294362..00000000 Binary files a/static/docs_imagem/tagoio/1563385125217-eok.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1576605304356-hps.png b/static/docs_imagem/tagoio/1576605304356-hps.png deleted file mode 100644 index 93283977..00000000 Binary files a/static/docs_imagem/tagoio/1576605304356-hps.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1576606418570-3DI.png b/static/docs_imagem/tagoio/1576606418570-3DI.png deleted file mode 100644 index 519246d0..00000000 Binary files a/static/docs_imagem/tagoio/1576606418570-3DI.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1576606566858-r_Q.png b/static/docs_imagem/tagoio/1576606566858-r_Q.png deleted file mode 100644 index 31c3e823..00000000 Binary files a/static/docs_imagem/tagoio/1576606566858-r_Q.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1600873613832-4Vc.png b/static/docs_imagem/tagoio/1600873613832-4Vc.png deleted file mode 100644 index 14982db6..00000000 Binary files a/static/docs_imagem/tagoio/1600873613832-4Vc.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1611084833441-Ers.png b/static/docs_imagem/tagoio/1611084833441-Ers.png deleted file mode 100644 index cae26cf3..00000000 Binary files a/static/docs_imagem/tagoio/1611084833441-Ers.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1624563795800-Zq8.png b/static/docs_imagem/tagoio/1624563795800-Zq8.png deleted file mode 100644 index 9cbbc5c2..00000000 Binary files a/static/docs_imagem/tagoio/1624563795800-Zq8.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1624878287784-MzI.png b/static/docs_imagem/tagoio/1624878287784-MzI.png deleted file mode 100644 index 36ece168..00000000 Binary files a/static/docs_imagem/tagoio/1624878287784-MzI.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/1627914062208-mNE.png b/static/docs_imagem/tagoio/1627914062208-mNE.png deleted file mode 100644 index 1959b5c7..00000000 Binary files a/static/docs_imagem/tagoio/1627914062208-mNE.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/Screen-20Shot-202019-10-28-20at-2016.41.44-bjQ.png b/static/docs_imagem/tagoio/Screen-20Shot-202019-10-28-20at-2016.41.44-bjQ.png deleted file mode 100644 index 3d60b9e6..00000000 Binary files a/static/docs_imagem/tagoio/Screen-20Shot-202019-10-28-20at-2016.41.44-bjQ.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/Screen-20Shot-202020-02-07-20at-205.44.26-20AM-NTA.png b/static/docs_imagem/tagoio/Screen-20Shot-202020-02-07-20at-205.44.26-20AM-NTA.png deleted file mode 100644 index 202b9159..00000000 Binary files a/static/docs_imagem/tagoio/Screen-20Shot-202020-02-07-20at-205.44.26-20AM-NTA.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/abs-telemetry-2.png b/static/docs_imagem/tagoio/abs-telemetry-2.png deleted file mode 100644 index c8d1d0ea..00000000 Binary files a/static/docs_imagem/tagoio/abs-telemetry-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/access-management-2.png b/static/docs_imagem/tagoio/access-management-2.png deleted file mode 100644 index 39c82295..00000000 Binary files a/static/docs_imagem/tagoio/access-management-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-3.png b/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-3.png deleted file mode 100644 index 147f4f1e..00000000 Binary files a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-4.png b/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-4.png deleted file mode 100644 index 759937b0..00000000 Binary files a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-5.png b/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-5.png deleted file mode 100644 index 9d3aa8b8..00000000 Binary files a/static/docs_imagem/tagoio/adding-image-selector-field-on-forms-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/adeunis-with-sigfox-2.png b/static/docs_imagem/tagoio/adeunis-with-sigfox-2.png deleted file mode 100644 index 64a9aabc..00000000 Binary files a/static/docs_imagem/tagoio/adeunis-with-sigfox-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/adeunis-with-sigfox-3.png b/static/docs_imagem/tagoio/adeunis-with-sigfox-3.png deleted file mode 100644 index 8cc4a301..00000000 Binary files a/static/docs_imagem/tagoio/adeunis-with-sigfox-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/analysis-service-2.png b/static/docs_imagem/tagoio/analysis-service-2.png deleted file mode 100644 index 0a24db56..00000000 Binary files a/static/docs_imagem/tagoio/analysis-service-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/angular-widget-3.gif b/static/docs_imagem/tagoio/angular-widget-3.gif deleted file mode 100644 index f4be4d7a..00000000 Binary files a/static/docs_imagem/tagoio/angular-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/authorization-2.png b/static/docs_imagem/tagoio/authorization-2.png deleted file mode 100644 index a66bc993..00000000 Binary files a/static/docs_imagem/tagoio/authorization-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/authorization-3.png b/static/docs_imagem/tagoio/authorization-3.png deleted file mode 100644 index 6204c615..00000000 Binary files a/static/docs_imagem/tagoio/authorization-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/beagle-bone-black-2.jpg b/static/docs_imagem/tagoio/beagle-bone-black-2.jpg deleted file mode 100644 index bb61ce64..00000000 Binary files a/static/docs_imagem/tagoio/beagle-bone-black-2.jpg and /dev/null differ diff --git a/static/docs_imagem/tagoio/beagle-bone-black-3.png b/static/docs_imagem/tagoio/beagle-bone-black-3.png deleted file mode 100644 index 3441d220..00000000 Binary files a/static/docs_imagem/tagoio/beagle-bone-black-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/beagle-bone-black-4.png b/static/docs_imagem/tagoio/beagle-bone-black-4.png deleted file mode 100644 index 75174126..00000000 Binary files a/static/docs_imagem/tagoio/beagle-bone-black-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/beagle-bone-black-5.png b/static/docs_imagem/tagoio/beagle-bone-black-5.png deleted file mode 100644 index 25f98d8a..00000000 Binary files a/static/docs_imagem/tagoio/beagle-bone-black-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/beagle-bone-black-6.png b/static/docs_imagem/tagoio/beagle-bone-black-6.png deleted file mode 100644 index 48e47858..00000000 Binary files a/static/docs_imagem/tagoio/beagle-bone-black-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/bp-dash-nOo.gif b/static/docs_imagem/tagoio/bp-dash-nOo.gif deleted file mode 100644 index 1fd3c172..00000000 Binary files a/static/docs_imagem/tagoio/bp-dash-nOo.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/card-widget-3.gif b/static/docs_imagem/tagoio/card-widget-3.gif deleted file mode 100644 index d8163eb3..00000000 Binary files a/static/docs_imagem/tagoio/card-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/card-widget-5.png b/static/docs_imagem/tagoio/card-widget-5.png deleted file mode 100644 index 32d32650..00000000 Binary files a/static/docs_imagem/tagoio/card-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/card-widget-6.gif b/static/docs_imagem/tagoio/card-widget-6.gif deleted file mode 100644 index a5bf196d..00000000 Binary files a/static/docs_imagem/tagoio/card-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/caution.png b/static/docs_imagem/tagoio/caution.png deleted file mode 100644 index 2fd09e2f..00000000 Binary files a/static/docs_imagem/tagoio/caution.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/claude_chat_mcp.png b/static/docs_imagem/tagoio/claude_chat_mcp.png deleted file mode 100644 index 1a8eb45d..00000000 Binary files a/static/docs_imagem/tagoio/claude_chat_mcp.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/comic-cartoon-toaster-vector-7023342-G8Y.jpg b/static/docs_imagem/tagoio/comic-cartoon-toaster-vector-7023342-G8Y.jpg deleted file mode 100644 index b36a48e2..00000000 Binary files a/static/docs_imagem/tagoio/comic-cartoon-toaster-vector-7023342-G8Y.jpg and /dev/null differ diff --git a/static/docs_imagem/tagoio/compose-widget-3.gif b/static/docs_imagem/tagoio/compose-widget-3.gif deleted file mode 100644 index 52aca41e..00000000 Binary files a/static/docs_imagem/tagoio/compose-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/compose-widget-5.gif b/static/docs_imagem/tagoio/compose-widget-5.gif deleted file mode 100644 index 92d9bbbf..00000000 Binary files a/static/docs_imagem/tagoio/compose-widget-5.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/compose-widget-7.gif b/static/docs_imagem/tagoio/compose-widget-7.gif deleted file mode 100644 index a490f9a7..00000000 Binary files a/static/docs_imagem/tagoio/compose-widget-7.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-10.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-10.png deleted file mode 100644 index 2687b034..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-10.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-2.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-2.png deleted file mode 100644 index 07379d2b..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-3.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-3.png deleted file mode 100644 index 633ad1c6..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-4.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-4.png deleted file mode 100644 index 46b37b5e..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-5.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-5.png deleted file mode 100644 index 8c540381..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-6.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-6.png deleted file mode 100644 index 13b98a06..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-7.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-7.png deleted file mode 100644 index b80687c3..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-7.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-8.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-8.png deleted file mode 100644 index 42652560..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-8.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-9.png b/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-9.png deleted file mode 100644 index fd39f2cf..00000000 Binary files a/static/docs_imagem/tagoio/connecting-zen15-power-using-smartthings-hub-9.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connector-overview-3.png b/static/docs_imagem/tagoio/connector-overview-3.png deleted file mode 100644 index 7e6d42ea..00000000 Binary files a/static/docs_imagem/tagoio/connector-overview-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connector-overview-4.png b/static/docs_imagem/tagoio/connector-overview-4.png deleted file mode 100644 index 0c9e32b1..00000000 Binary files a/static/docs_imagem/tagoio/connector-overview-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/connector-overview-5.png b/static/docs_imagem/tagoio/connector-overview-5.png deleted file mode 100644 index 063cb9ce..00000000 Binary files a/static/docs_imagem/tagoio/connector-overview-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/console-for-debug-2.png b/static/docs_imagem/tagoio/console-for-debug-2.png deleted file mode 100644 index 56939fab..00000000 Binary files a/static/docs_imagem/tagoio/console-for-debug-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-a-network-integration-2.png b/static/docs_imagem/tagoio/creating-a-network-integration-2.png deleted file mode 100644 index 8bd027be..00000000 Binary files a/static/docs_imagem/tagoio/creating-a-network-integration-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-a-network-integration-3.png b/static/docs_imagem/tagoio/creating-a-network-integration-3.png deleted file mode 100644 index 213c5d90..00000000 Binary files a/static/docs_imagem/tagoio/creating-a-network-integration-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-a-network-integration-4.png b/static/docs_imagem/tagoio/creating-a-network-integration-4.png deleted file mode 100644 index 1f2801fe..00000000 Binary files a/static/docs_imagem/tagoio/creating-a-network-integration-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-a-network-integration-5.png b/static/docs_imagem/tagoio/creating-a-network-integration-5.png deleted file mode 100644 index 6f90b7ca..00000000 Binary files a/static/docs_imagem/tagoio/creating-a-network-integration-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-a-policy-2.png b/static/docs_imagem/tagoio/creating-a-policy-2.png deleted file mode 100644 index dc96175b..00000000 Binary files a/static/docs_imagem/tagoio/creating-a-policy-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-3.png b/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-3.png deleted file mode 100644 index e15bdef3..00000000 Binary files a/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-4.png b/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-4.png deleted file mode 100644 index dc8beebd..00000000 Binary files a/static/docs_imagem/tagoio/creating-dynamic-dropdown-selection-using-forms-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/creatingDevice.gif b/static/docs_imagem/tagoio/creatingDevice.gif new file mode 100644 index 00000000..62e30729 Binary files /dev/null and b/static/docs_imagem/tagoio/creatingDevice.gif differ diff --git a/static/docs_imagem/tagoio/ctower_device_statistics.png b/static/docs_imagem/tagoio/ctower_device_statistics.png deleted file mode 100644 index b1ccc824..00000000 Binary files a/static/docs_imagem/tagoio/ctower_device_statistics.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/custom-widget-3.gif b/static/docs_imagem/tagoio/custom-widget-3.gif deleted file mode 100644 index 073d4d96..00000000 Binary files a/static/docs_imagem/tagoio/custom-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/custom-widget-4.gif b/static/docs_imagem/tagoio/custom-widget-4.gif deleted file mode 100644 index 36fc0679..00000000 Binary files a/static/docs_imagem/tagoio/custom-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/custom-widget-6.png b/static/docs_imagem/tagoio/custom-widget-6.png deleted file mode 100644 index 59e64547..00000000 Binary files a/static/docs_imagem/tagoio/custom-widget-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/custom_widget_5 b/static/docs_imagem/tagoio/custom_widget_5 deleted file mode 100644 index bfc0380c..00000000 Binary files a/static/docs_imagem/tagoio/custom_widget_5 and /dev/null differ diff --git a/static/docs_imagem/tagoio/cylinder-widget-3.gif b/static/docs_imagem/tagoio/cylinder-widget-3.gif deleted file mode 100644 index 2bad29c3..00000000 Binary files a/static/docs_imagem/tagoio/cylinder-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/cylinder-widget-5.gif b/static/docs_imagem/tagoio/cylinder-widget-5.gif deleted file mode 100644 index dd176d1f..00000000 Binary files a/static/docs_imagem/tagoio/cylinder-widget-5.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/dashboard-icons-3.png b/static/docs_imagem/tagoio/dashboard-icons-3.png deleted file mode 100644 index 008e4058..00000000 Binary files a/static/docs_imagem/tagoio/dashboard-icons-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dashboard-icons-4.png b/static/docs_imagem/tagoio/dashboard-icons-4.png deleted file mode 100644 index f10c1abc..00000000 Binary files a/static/docs_imagem/tagoio/dashboard-icons-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dashboard-icons-5.png b/static/docs_imagem/tagoio/dashboard-icons-5.png deleted file mode 100644 index 0158f5bd..00000000 Binary files a/static/docs_imagem/tagoio/dashboard-icons-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/defining-actions-2.png b/static/docs_imagem/tagoio/defining-actions-2.png deleted file mode 100644 index 2ba6db88..00000000 Binary files a/static/docs_imagem/tagoio/defining-actions-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/defining-permissions-2.png b/static/docs_imagem/tagoio/defining-permissions-2.png deleted file mode 100644 index 013827fe..00000000 Binary files a/static/docs_imagem/tagoio/defining-permissions-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/defining-targets-2.png b/static/docs_imagem/tagoio/defining-targets-2.png deleted file mode 100644 index 8faa379f..00000000 Binary files a/static/docs_imagem/tagoio/defining-targets-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/deleting-data-2.png b/static/docs_imagem/tagoio/deleting-data-2.png deleted file mode 100644 index af42a0ef..00000000 Binary files a/static/docs_imagem/tagoio/deleting-data-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/deleting-your-account-2.png b/static/docs_imagem/tagoio/deleting-your-account-2.png deleted file mode 100644 index a9005583..00000000 Binary files a/static/docs_imagem/tagoio/deleting-your-account-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/device-emulator-functions-3.png b/static/docs_imagem/tagoio/device-emulator-functions-3.png deleted file mode 100644 index 6c02fc01..00000000 Binary files a/static/docs_imagem/tagoio/device-emulator-functions-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/device-emulator-functions-4.png b/static/docs_imagem/tagoio/device-emulator-functions-4.png deleted file mode 100644 index 1aef7873..00000000 Binary files a/static/docs_imagem/tagoio/device-emulator-functions-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/device-emulator-functions-5.png b/static/docs_imagem/tagoio/device-emulator-functions-5.png deleted file mode 100644 index f6c4b5f3..00000000 Binary files a/static/docs_imagem/tagoio/device-emulator-functions-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/device-emulator-functions-6.png b/static/docs_imagem/tagoio/device-emulator-functions-6.png deleted file mode 100644 index 5af0fbe6..00000000 Binary files a/static/docs_imagem/tagoio/device-emulator-functions-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/device-list-widget-3.png b/static/docs_imagem/tagoio/device-list-widget-3.png deleted file mode 100644 index cb3492d2..00000000 Binary files a/static/docs_imagem/tagoio/device-list-widget-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/deviceCreation2.gif b/static/docs_imagem/tagoio/deviceCreation2.gif new file mode 100644 index 00000000..3b753493 Binary files /dev/null and b/static/docs_imagem/tagoio/deviceCreation2.gif differ diff --git a/static/docs_imagem/tagoio/device_limit_ctower.png b/static/docs_imagem/tagoio/device_limit_ctower.png deleted file mode 100644 index 5b5bacf7..00000000 Binary files a/static/docs_imagem/tagoio/device_limit_ctower.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/devicedataflowupdated.png b/static/docs_imagem/tagoio/devicedataflowupdated.png new file mode 100644 index 00000000..d94afe0b Binary files /dev/null and b/static/docs_imagem/tagoio/devicedataflowupdated.png differ diff --git a/static/docs_imagem/tagoio/dial-widget-3.gif b/static/docs_imagem/tagoio/dial-widget-3.gif deleted file mode 100644 index 263e7e54..00000000 Binary files a/static/docs_imagem/tagoio/dial-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/distributing-analysis-2.png b/static/docs_imagem/tagoio/distributing-analysis-2.png deleted file mode 100644 index 3ca95d53..00000000 Binary files a/static/docs_imagem/tagoio/distributing-analysis-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/distributing-analysis-3.png b/static/docs_imagem/tagoio/distributing-analysis-3.png deleted file mode 100644 index acdb34d2..00000000 Binary files a/static/docs_imagem/tagoio/distributing-analysis-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/distributing-analysis-4.png b/static/docs_imagem/tagoio/distributing-analysis-4.png deleted file mode 100644 index f40bb649..00000000 Binary files a/static/docs_imagem/tagoio/distributing-analysis-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/distributing-analysis-5.png b/static/docs_imagem/tagoio/distributing-analysis-5.png deleted file mode 100644 index 6cb365dd..00000000 Binary files a/static/docs_imagem/tagoio/distributing-analysis-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/distributing-analysis-6.png b/static/docs_imagem/tagoio/distributing-analysis-6.png deleted file mode 100644 index e45de612..00000000 Binary files a/static/docs_imagem/tagoio/distributing-analysis-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/downlinks-using-dashboards-2.png b/static/docs_imagem/tagoio/downlinks-using-dashboards-2.png deleted file mode 100644 index 2cfb6f25..00000000 Binary files a/static/docs_imagem/tagoio/downlinks-using-dashboards-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/downlinks-using-dashboards-3.png b/static/docs_imagem/tagoio/downlinks-using-dashboards-3.png deleted file mode 100644 index 4f3eec7e..00000000 Binary files a/static/docs_imagem/tagoio/downlinks-using-dashboards-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dropdown_parameter.png b/static/docs_imagem/tagoio/dropdown_parameter.png deleted file mode 100644 index 6f90b7ca..00000000 Binary files a/static/docs_imagem/tagoio/dropdown_parameter.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dynamic-table-widget-4.png b/static/docs_imagem/tagoio/dynamic-table-widget-4.png deleted file mode 100644 index 30b7ffa4..00000000 Binary files a/static/docs_imagem/tagoio/dynamic-table-widget-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dynamic-table-widget-5.png b/static/docs_imagem/tagoio/dynamic-table-widget-5.png deleted file mode 100644 index 1dd8d40f..00000000 Binary files a/static/docs_imagem/tagoio/dynamic-table-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/dynamic-table-widget-6.gif b/static/docs_imagem/tagoio/dynamic-table-widget-6.gif deleted file mode 100644 index f70d7a06..00000000 Binary files a/static/docs_imagem/tagoio/dynamic-table-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/embedding-widgets-to-your-website-2.gif b/static/docs_imagem/tagoio/embedding-widgets-to-your-website-2.gif deleted file mode 100644 index 9b5db24c..00000000 Binary files a/static/docs_imagem/tagoio/embedding-widgets-to-your-website-2.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/embedding-widgets-to-your-website-3.png b/static/docs_imagem/tagoio/embedding-widgets-to-your-website-3.png deleted file mode 100644 index a80be3ce..00000000 Binary files a/static/docs_imagem/tagoio/embedding-widgets-to-your-website-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/everynet-lorawan-2.jpg b/static/docs_imagem/tagoio/everynet-lorawan-2.jpg deleted file mode 100644 index 2574d060..00000000 Binary files a/static/docs_imagem/tagoio/everynet-lorawan-2.jpg and /dev/null differ diff --git a/static/docs_imagem/tagoio/everynet-lorawan-4.png b/static/docs_imagem/tagoio/everynet-lorawan-4.png deleted file mode 100644 index a68fafa1..00000000 Binary files a/static/docs_imagem/tagoio/everynet-lorawan-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/everynet-lorawan-5.png b/static/docs_imagem/tagoio/everynet-lorawan-5.png deleted file mode 100644 index 0a6af028..00000000 Binary files a/static/docs_imagem/tagoio/everynet-lorawan-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/everynet-lorawan-6.png b/static/docs_imagem/tagoio/everynet-lorawan-6.png deleted file mode 100644 index 548a3fef..00000000 Binary files a/static/docs_imagem/tagoio/everynet-lorawan-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/exclamation-4.png b/static/docs_imagem/tagoio/exclamation-4.png deleted file mode 100644 index 7003e629..00000000 Binary files a/static/docs_imagem/tagoio/exclamation-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-00c113a0.png b/static/docs_imagem/tagoio/external-00c113a0.png deleted file mode 100644 index f2f66b8a..00000000 Binary files a/static/docs_imagem/tagoio/external-00c113a0.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-122ff21d.png b/static/docs_imagem/tagoio/external-122ff21d.png deleted file mode 100644 index 5d989bb3..00000000 Binary files a/static/docs_imagem/tagoio/external-122ff21d.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-41c105e7.png b/static/docs_imagem/tagoio/external-41c105e7.png deleted file mode 100644 index 12dd9523..00000000 Binary files a/static/docs_imagem/tagoio/external-41c105e7.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-474cf6ac.png b/static/docs_imagem/tagoio/external-474cf6ac.png deleted file mode 100644 index 8aeb03bf..00000000 Binary files a/static/docs_imagem/tagoio/external-474cf6ac.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-525092fc.png b/static/docs_imagem/tagoio/external-525092fc.png deleted file mode 100644 index 32225e5d..00000000 Binary files a/static/docs_imagem/tagoio/external-525092fc.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-549c623a.png b/static/docs_imagem/tagoio/external-549c623a.png deleted file mode 100644 index 1b2fc3c4..00000000 Binary files a/static/docs_imagem/tagoio/external-549c623a.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-6c842fb5.png b/static/docs_imagem/tagoio/external-6c842fb5.png deleted file mode 100644 index 7c7c01f6..00000000 Binary files a/static/docs_imagem/tagoio/external-6c842fb5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-7c017b2d.png b/static/docs_imagem/tagoio/external-7c017b2d.png deleted file mode 100644 index ba6828a4..00000000 Binary files a/static/docs_imagem/tagoio/external-7c017b2d.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-969e5674.png b/static/docs_imagem/tagoio/external-969e5674.png deleted file mode 100644 index 6d385dd0..00000000 Binary files a/static/docs_imagem/tagoio/external-969e5674.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-bf3190c0.png b/static/docs_imagem/tagoio/external-bf3190c0.png deleted file mode 100644 index 4aaa0b6e..00000000 Binary files a/static/docs_imagem/tagoio/external-bf3190c0.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-d3b441c9.png b/static/docs_imagem/tagoio/external-d3b441c9.png deleted file mode 100644 index 04768b63..00000000 Binary files a/static/docs_imagem/tagoio/external-d3b441c9.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-eae39401.png b/static/docs_imagem/tagoio/external-eae39401.png deleted file mode 100644 index 4f492d61..00000000 Binary files a/static/docs_imagem/tagoio/external-eae39401.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-ef92af1a.png b/static/docs_imagem/tagoio/external-ef92af1a.png deleted file mode 100644 index 3d114a40..00000000 Binary files a/static/docs_imagem/tagoio/external-ef92af1a.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-f4bf5eb6.png b/static/docs_imagem/tagoio/external-f4bf5eb6.png deleted file mode 100644 index 6d4cb677..00000000 Binary files a/static/docs_imagem/tagoio/external-f4bf5eb6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-f91f78f4.png b/static/docs_imagem/tagoio/external-f91f78f4.png deleted file mode 100644 index 52ee1ef9..00000000 Binary files a/static/docs_imagem/tagoio/external-f91f78f4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/external-notanymore.gif b/static/docs_imagem/tagoio/external-notanymore.gif new file mode 100644 index 00000000..fa0358ab Binary files /dev/null and b/static/docs_imagem/tagoio/external-notanymore.gif differ diff --git a/static/docs_imagem/tagoio/files-2.gif b/static/docs_imagem/tagoio/files-2.gif deleted file mode 100644 index eb92acb2..00000000 Binary files a/static/docs_imagem/tagoio/files-2.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/files-3.png b/static/docs_imagem/tagoio/files-3.png deleted file mode 100644 index b54689e5..00000000 Binary files a/static/docs_imagem/tagoio/files-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/filesvid.gif b/static/docs_imagem/tagoio/filesvid.gif new file mode 100644 index 00000000..bfab293a Binary files /dev/null and b/static/docs_imagem/tagoio/filesvid.gif differ diff --git a/static/docs_imagem/tagoio/filtered-variables-3.png b/static/docs_imagem/tagoio/filtered-variables-3.png deleted file mode 100644 index 5bfed1d1..00000000 Binary files a/static/docs_imagem/tagoio/filtered-variables-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/filtered-variables-4.gif b/static/docs_imagem/tagoio/filtered-variables-4.gif deleted file mode 100644 index cf0135cc..00000000 Binary files a/static/docs_imagem/tagoio/filtered-variables-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/form-fields-visibility-3.png b/static/docs_imagem/tagoio/form-fields-visibility-3.png deleted file mode 100644 index 0022f6bb..00000000 Binary files a/static/docs_imagem/tagoio/form-fields-visibility-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/form-fields-visibility-4.png b/static/docs_imagem/tagoio/form-fields-visibility-4.png deleted file mode 100644 index 42b74c22..00000000 Binary files a/static/docs_imagem/tagoio/form-fields-visibility-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/form-fields-visibility-5.png b/static/docs_imagem/tagoio/form-fields-visibility-5.png deleted file mode 100644 index a591a396..00000000 Binary files a/static/docs_imagem/tagoio/form-fields-visibility-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/gauge-data-range-format-3.png b/static/docs_imagem/tagoio/gauge-data-range-format-3.png deleted file mode 100644 index 604c3b95..00000000 Binary files a/static/docs_imagem/tagoio/gauge-data-range-format-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/gauge-data-range-format-4.png b/static/docs_imagem/tagoio/gauge-data-range-format-4.png deleted file mode 100644 index 12003c99..00000000 Binary files a/static/docs_imagem/tagoio/gauge-data-range-format-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/geofences-in-map-widgets-8.png b/static/docs_imagem/tagoio/geofences-in-map-widgets-8.png deleted file mode 100644 index 57e88c0d..00000000 Binary files a/static/docs_imagem/tagoio/geofences-in-map-widgets-8.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/grouping-dashboards-3.png b/static/docs_imagem/tagoio/grouping-dashboards-3.png deleted file mode 100644 index f99fc5eb..00000000 Binary files a/static/docs_imagem/tagoio/grouping-dashboards-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/heat-map-widget-3.gif b/static/docs_imagem/tagoio/heat-map-widget-3.gif deleted file mode 100644 index 91cf78c5..00000000 Binary files a/static/docs_imagem/tagoio/heat-map-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/heat-map-widget-7.png b/static/docs_imagem/tagoio/heat-map-widget-7.png deleted file mode 100644 index cbf1fc14..00000000 Binary files a/static/docs_imagem/tagoio/heat-map-widget-7.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/horizontal-bar-widget-4.gif b/static/docs_imagem/tagoio/horizontal-bar-widget-4.gif deleted file mode 100644 index ed40a29e..00000000 Binary files a/static/docs_imagem/tagoio/horizontal-bar-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/horizontal-bar-widget-5.png b/static/docs_imagem/tagoio/horizontal-bar-widget-5.png deleted file mode 100644 index 28f873bd..00000000 Binary files a/static/docs_imagem/tagoio/horizontal-bar-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/horizontal-bar-widget-6.gif b/static/docs_imagem/tagoio/horizontal-bar-widget-6.gif deleted file mode 100644 index 9013321b..00000000 Binary files a/static/docs_imagem/tagoio/horizontal-bar-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/icons-widget-4.gif b/static/docs_imagem/tagoio/icons-widget-4.gif deleted file mode 100644 index 43c52905..00000000 Binary files a/static/docs_imagem/tagoio/icons-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-10.png b/static/docs_imagem/tagoio/image-marker-widget-10.png deleted file mode 100644 index 90dca6c3..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-10.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-11.gif b/static/docs_imagem/tagoio/image-marker-widget-11.gif deleted file mode 100644 index 95950e5c..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-11.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-12.png b/static/docs_imagem/tagoio/image-marker-widget-12.png deleted file mode 100644 index fd7d920e..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-12.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-13.gif b/static/docs_imagem/tagoio/image-marker-widget-13.gif deleted file mode 100644 index 47e3ab7c..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-13.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-3.gif b/static/docs_imagem/tagoio/image-marker-widget-3.gif deleted file mode 100644 index 89916132..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-6.png b/static/docs_imagem/tagoio/image-marker-widget-6.png deleted file mode 100644 index 3868e036..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-7.gif b/static/docs_imagem/tagoio/image-marker-widget-7.gif deleted file mode 100644 index f17c1326..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-7.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-8.gif b/static/docs_imagem/tagoio/image-marker-widget-8.gif deleted file mode 100644 index 815f928a..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-8.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/image-marker-widget-9.png b/static/docs_imagem/tagoio/image-marker-widget-9.png deleted file mode 100644 index 28f64656..00000000 Binary files a/static/docs_imagem/tagoio/image-marker-widget-9.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/image.png b/static/docs_imagem/tagoio/image.png new file mode 100644 index 00000000..6fe1fd90 Binary files /dev/null and b/static/docs_imagem/tagoio/image.png differ diff --git a/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-3.png b/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-3.png deleted file mode 100644 index b9c5b144..00000000 Binary files a/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-4.png b/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-4.png deleted file mode 100644 index d56bdc19..00000000 Binary files a/static/docs_imagem/tagoio/images-and-links-in-the-maps-pins-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/import-export-for-dictionary-2.png b/static/docs_imagem/tagoio/import-export-for-dictionary-2.png deleted file mode 100644 index ab7abc9e..00000000 Binary files a/static/docs_imagem/tagoio/import-export-for-dictionary-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/info-8.png b/static/docs_imagem/tagoio/info-8.png deleted file mode 100644 index 5ac67b1d..00000000 Binary files a/static/docs_imagem/tagoio/info-8.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/input-control-widget-6.gif b/static/docs_imagem/tagoio/input-control-widget-6.gif deleted file mode 100644 index a0e53533..00000000 Binary files a/static/docs_imagem/tagoio/input-control-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/input-control-widget-7.gif b/static/docs_imagem/tagoio/input-control-widget-7.gif deleted file mode 100644 index 09fffd1a..00000000 Binary files a/static/docs_imagem/tagoio/input-control-widget-7.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/keypad-visualization-3.png b/static/docs_imagem/tagoio/keypad-visualization-3.png deleted file mode 100644 index b30b0f04..00000000 Binary files a/static/docs_imagem/tagoio/keypad-visualization-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/keypad-visualization-4.png b/static/docs_imagem/tagoio/keypad-visualization-4.png deleted file mode 100644 index 73aa05e0..00000000 Binary files a/static/docs_imagem/tagoio/keypad-visualization-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/keypad-widget-3.gif b/static/docs_imagem/tagoio/keypad-widget-3.gif deleted file mode 100644 index 5060dd83..00000000 Binary files a/static/docs_imagem/tagoio/keypad-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/keypad-widget-5.png b/static/docs_imagem/tagoio/keypad-widget-5.png deleted file mode 100644 index 05068d1a..00000000 Binary files a/static/docs_imagem/tagoio/keypad-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/lights.png b/static/docs_imagem/tagoio/lights.png deleted file mode 100644 index f441ed7f..00000000 Binary files a/static/docs_imagem/tagoio/lights.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/line-chart-widget-4.gif b/static/docs_imagem/tagoio/line-chart-widget-4.gif deleted file mode 100644 index 1ca67bc4..00000000 Binary files a/static/docs_imagem/tagoio/line-chart-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/live-inspector-3.png b/static/docs_imagem/tagoio/live-inspector-3.png deleted file mode 100644 index 6162998a..00000000 Binary files a/static/docs_imagem/tagoio/live-inspector-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/loriot-lorawan-2.png b/static/docs_imagem/tagoio/loriot-lorawan-2.png deleted file mode 100644 index d2f294eb..00000000 Binary files a/static/docs_imagem/tagoio/loriot-lorawan-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/loriot-lorawan-3.png b/static/docs_imagem/tagoio/loriot-lorawan-3.png deleted file mode 100644 index c7bdf46f..00000000 Binary files a/static/docs_imagem/tagoio/loriot-lorawan-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/loriot-lorawan-4.png b/static/docs_imagem/tagoio/loriot-lorawan-4.png deleted file mode 100644 index 1f4ce10e..00000000 Binary files a/static/docs_imagem/tagoio/loriot-lorawan-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/machineq-lorawan-2.png b/static/docs_imagem/tagoio/machineq-lorawan-2.png deleted file mode 100644 index cf0ba462..00000000 Binary files a/static/docs_imagem/tagoio/machineq-lorawan-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/machineq-lorawan-3.png b/static/docs_imagem/tagoio/machineq-lorawan-3.png deleted file mode 100644 index ef0e889d..00000000 Binary files a/static/docs_imagem/tagoio/machineq-lorawan-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-filters-4.png b/static/docs_imagem/tagoio/map-filters-4.png deleted file mode 100644 index 77902a39..00000000 Binary files a/static/docs_imagem/tagoio/map-filters-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-filters-5.png b/static/docs_imagem/tagoio/map-filters-5.png deleted file mode 100644 index 1da12c2f..00000000 Binary files a/static/docs_imagem/tagoio/map-filters-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-layer-gis-3.gif b/static/docs_imagem/tagoio/map-layer-gis-3.gif deleted file mode 100644 index 41b4eb61..00000000 Binary files a/static/docs_imagem/tagoio/map-layer-gis-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-layer-gis-4.png b/static/docs_imagem/tagoio/map-layer-gis-4.png deleted file mode 100644 index 1a52744d..00000000 Binary files a/static/docs_imagem/tagoio/map-layer-gis-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-layer-gis-5.gif b/static/docs_imagem/tagoio/map-layer-gis-5.gif deleted file mode 100644 index 693573d8..00000000 Binary files a/static/docs_imagem/tagoio/map-layer-gis-5.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/map-layer-gis-6.gif b/static/docs_imagem/tagoio/map-layer-gis-6.gif deleted file mode 100644 index 5f738a04..00000000 Binary files a/static/docs_imagem/tagoio/map-layer-gis-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/mcp_diagram.png b/static/docs_imagem/tagoio/mcp_diagram.png deleted file mode 100644 index 656cea3e..00000000 Binary files a/static/docs_imagem/tagoio/mcp_diagram.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqq_permission.png b/static/docs_imagem/tagoio/mqq_permission.png deleted file mode 100644 index 982a5870..00000000 Binary files a/static/docs_imagem/tagoio/mqq_permission.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-4.png b/static/docs_imagem/tagoio/mqtt-4.png deleted file mode 100644 index fbdd373b..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-5.png b/static/docs_imagem/tagoio/mqtt-5.png deleted file mode 100644 index 9af9e89d..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-6.png b/static/docs_imagem/tagoio/mqtt-6.png deleted file mode 100644 index a3fdac7e..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-publishing-and-subscribing-3.png b/static/docs_imagem/tagoio/mqtt-publishing-and-subscribing-3.png deleted file mode 100644 index 54535084..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-publishing-and-subscribing-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-2.png b/static/docs_imagem/tagoio/mqtt-with-sensor-tag-2.png deleted file mode 100644 index a2a2ded5..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-3.png b/static/docs_imagem/tagoio/mqtt-with-sensor-tag-3.png deleted file mode 100644 index 318732eb..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-4.png b/static/docs_imagem/tagoio/mqtt-with-sensor-tag-4.png deleted file mode 100644 index d2afdf4f..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-5.png b/static/docs_imagem/tagoio/mqtt-with-sensor-tag-5.png deleted file mode 100644 index 09fa129d..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-6.png b/static/docs_imagem/tagoio/mqtt-with-sensor-tag-6.png deleted file mode 100644 index 091d372c..00000000 Binary files a/static/docs_imagem/tagoio/mqtt-with-sensor-tag-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/multiple-charts-widget-4.gif b/static/docs_imagem/tagoio/multiple-charts-widget-4.gif deleted file mode 100644 index 4fe332cc..00000000 Binary files a/static/docs_imagem/tagoio/multiple-charts-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/multiple-charts-widget-5.png b/static/docs_imagem/tagoio/multiple-charts-widget-5.png deleted file mode 100644 index 778d61be..00000000 Binary files a/static/docs_imagem/tagoio/multiple-charts-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/multiple-charts-widget-6.gif b/static/docs_imagem/tagoio/multiple-charts-widget-6.gif deleted file mode 100644 index c105e627..00000000 Binary files a/static/docs_imagem/tagoio/multiple-charts-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/multiple-charts-widget-7.gif b/static/docs_imagem/tagoio/multiple-charts-widget-7.gif deleted file mode 100644 index 58c0e32e..00000000 Binary files a/static/docs_imagem/tagoio/multiple-charts-widget-7.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/notification-2.png b/static/docs_imagem/tagoio/notification-2.png deleted file mode 100644 index 9f08416b..00000000 Binary files a/static/docs_imagem/tagoio/notification-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/notification-3.png b/static/docs_imagem/tagoio/notification-3.png deleted file mode 100644 index 457f7f8f..00000000 Binary files a/static/docs_imagem/tagoio/notification-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/notification-4.png b/static/docs_imagem/tagoio/notification-4.png deleted file mode 100644 index ab307f4c..00000000 Binary files a/static/docs_imagem/tagoio/notification-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/notification-5.png b/static/docs_imagem/tagoio/notification-5.png deleted file mode 100644 index 7dfd4a3e..00000000 Binary files a/static/docs_imagem/tagoio/notification-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/notifications-for-users-3.png b/static/docs_imagem/tagoio/notifications-for-users-3.png deleted file mode 100644 index 034bd083..00000000 Binary files a/static/docs_imagem/tagoio/notifications-for-users-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/orbiwise-lorawan-2.jpg b/static/docs_imagem/tagoio/orbiwise-lorawan-2.jpg deleted file mode 100644 index f418ab46..00000000 Binary files a/static/docs_imagem/tagoio/orbiwise-lorawan-2.jpg and /dev/null differ diff --git a/static/docs_imagem/tagoio/paylot_xkit-i8s.png b/static/docs_imagem/tagoio/paylot_xkit-i8s.png deleted file mode 100644 index 0f2de374..00000000 Binary files a/static/docs_imagem/tagoio/paylot_xkit-i8s.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/peek_36.gif b/static/docs_imagem/tagoio/peek_36.gif new file mode 100644 index 00000000..dcfa6d5a Binary files /dev/null and b/static/docs_imagem/tagoio/peek_36.gif differ diff --git a/static/docs_imagem/tagoio/peek_37.gif b/static/docs_imagem/tagoio/peek_37.gif new file mode 100644 index 00000000..2eda038a Binary files /dev/null and b/static/docs_imagem/tagoio/peek_37.gif differ diff --git a/static/docs_imagem/tagoio/pie-widget-3.gif b/static/docs_imagem/tagoio/pie-widget-3.gif deleted file mode 100644 index ed4fcc1d..00000000 Binary files a/static/docs_imagem/tagoio/pie-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/profile_limit_ctower.png b/static/docs_imagem/tagoio/profile_limit_ctower.png deleted file mode 100644 index e99447e1..00000000 Binary files a/static/docs_imagem/tagoio/profile_limit_ctower.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/push-button-widget-3.gif b/static/docs_imagem/tagoio/push-button-widget-3.gif deleted file mode 100644 index 618b0a44..00000000 Binary files a/static/docs_imagem/tagoio/push-button-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/queclink-gps-2.png b/static/docs_imagem/tagoio/queclink-gps-2.png deleted file mode 100644 index cd453890..00000000 Binary files a/static/docs_imagem/tagoio/queclink-gps-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/queclink-gps-3.png b/static/docs_imagem/tagoio/queclink-gps-3.png deleted file mode 100644 index 5808ee9b..00000000 Binary files a/static/docs_imagem/tagoio/queclink-gps-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/queclink-gps-4.png b/static/docs_imagem/tagoio/queclink-gps-4.png deleted file mode 100644 index 3659f595..00000000 Binary files a/static/docs_imagem/tagoio/queclink-gps-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/radiobridge-devices-2.png b/static/docs_imagem/tagoio/radiobridge-devices-2.png deleted file mode 100644 index 03bb2727..00000000 Binary files a/static/docs_imagem/tagoio/radiobridge-devices-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/radiobridge-devices-3.png b/static/docs_imagem/tagoio/radiobridge-devices-3.png deleted file mode 100644 index 0766a2a9..00000000 Binary files a/static/docs_imagem/tagoio/radiobridge-devices-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/radiobridge-devices-4.png b/static/docs_imagem/tagoio/radiobridge-devices-4.png deleted file mode 100644 index 3e23a708..00000000 Binary files a/static/docs_imagem/tagoio/radiobridge-devices-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/raspberry-pi-2.png b/static/docs_imagem/tagoio/raspberry-pi-2.png deleted file mode 100644 index dd49e3a0..00000000 Binary files a/static/docs_imagem/tagoio/raspberry-pi-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761078136729.png b/static/docs_imagem/tagoio/rounded-image-1761078136729.png new file mode 100644 index 00000000..ebb5c145 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761078136729.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761078341385.png b/static/docs_imagem/tagoio/rounded-image-1761078341385.png new file mode 100644 index 00000000..6928efc1 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761078341385.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761140461575.png b/static/docs_imagem/tagoio/rounded-image-1761140461575.png new file mode 100644 index 00000000..93c40134 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761140461575.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761141519422.png b/static/docs_imagem/tagoio/rounded-image-1761141519422.png new file mode 100644 index 00000000..e9ad01f0 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761141519422.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761142560772.png b/static/docs_imagem/tagoio/rounded-image-1761142560772.png new file mode 100644 index 00000000..f11aabe5 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761142560772.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761143169484.png b/static/docs_imagem/tagoio/rounded-image-1761143169484.png new file mode 100644 index 00000000..58895675 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761143169484.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761143952960.png b/static/docs_imagem/tagoio/rounded-image-1761143952960.png new file mode 100644 index 00000000..98902c7f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761143952960.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761144346438.png b/static/docs_imagem/tagoio/rounded-image-1761144346438.png new file mode 100644 index 00000000..3e9b7fb6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761144346438.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761144951026.png b/static/docs_imagem/tagoio/rounded-image-1761144951026.png new file mode 100644 index 00000000..369c950c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761144951026.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761145033874.png b/static/docs_imagem/tagoio/rounded-image-1761145033874.png new file mode 100644 index 00000000..083519d4 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761145033874.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761160129581.png b/static/docs_imagem/tagoio/rounded-image-1761160129581.png new file mode 100644 index 00000000..14aaa8ce Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761160129581.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761224381413.png b/static/docs_imagem/tagoio/rounded-image-1761224381413.png new file mode 100644 index 00000000..fedcd23b Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761224381413.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761224471130.png b/static/docs_imagem/tagoio/rounded-image-1761224471130.png new file mode 100644 index 00000000..98c2b2f7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761224471130.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761226314440.png b/static/docs_imagem/tagoio/rounded-image-1761226314440.png new file mode 100644 index 00000000..61b76bd3 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761226314440.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761226494988.png b/static/docs_imagem/tagoio/rounded-image-1761226494988.png new file mode 100644 index 00000000..9a1fccb6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761226494988.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761226750000.png b/static/docs_imagem/tagoio/rounded-image-1761226750000.png new file mode 100644 index 00000000..6c589cd4 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761226750000.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761227083363.png b/static/docs_imagem/tagoio/rounded-image-1761227083363.png new file mode 100644 index 00000000..11aeea34 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761227083363.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761309633786.png b/static/docs_imagem/tagoio/rounded-image-1761309633786.png new file mode 100644 index 00000000..c25d718a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761309633786.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761311243395.png b/static/docs_imagem/tagoio/rounded-image-1761311243395.png new file mode 100644 index 00000000..2aade5f2 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761311243395.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761311392776.png b/static/docs_imagem/tagoio/rounded-image-1761311392776.png new file mode 100644 index 00000000..b69f9a3f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761311392776.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761311582465.png b/static/docs_imagem/tagoio/rounded-image-1761311582465.png new file mode 100644 index 00000000..9fe71d0d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761311582465.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761311651518.png b/static/docs_imagem/tagoio/rounded-image-1761311651518.png new file mode 100644 index 00000000..b120abdd Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761311651518.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761311943540.png b/static/docs_imagem/tagoio/rounded-image-1761311943540.png new file mode 100644 index 00000000..a201a0b6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761311943540.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761312069480.png b/static/docs_imagem/tagoio/rounded-image-1761312069480.png new file mode 100644 index 00000000..a7e96b5f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761312069480.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761312428484.png b/static/docs_imagem/tagoio/rounded-image-1761312428484.png new file mode 100644 index 00000000..4168c844 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761312428484.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761312647438.png b/static/docs_imagem/tagoio/rounded-image-1761312647438.png new file mode 100644 index 00000000..4e66be66 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761312647438.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761312825480.png b/static/docs_imagem/tagoio/rounded-image-1761312825480.png new file mode 100644 index 00000000..98f2b1df Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761312825480.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761313093242.png b/static/docs_imagem/tagoio/rounded-image-1761313093242.png new file mode 100644 index 00000000..bce6555e Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761313093242.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761313210646.png b/static/docs_imagem/tagoio/rounded-image-1761313210646.png new file mode 100644 index 00000000..db56901a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761313210646.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761748510973.png b/static/docs_imagem/tagoio/rounded-image-1761748510973.png new file mode 100644 index 00000000..98dda11d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761748510973.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761748581641.png b/static/docs_imagem/tagoio/rounded-image-1761748581641.png new file mode 100644 index 00000000..1d120640 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761748581641.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761748615221.png b/static/docs_imagem/tagoio/rounded-image-1761748615221.png new file mode 100644 index 00000000..5cafd0ca Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761748615221.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761748797456.png b/static/docs_imagem/tagoio/rounded-image-1761748797456.png new file mode 100644 index 00000000..df57cce0 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761748797456.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761749001761.png b/static/docs_imagem/tagoio/rounded-image-1761749001761.png new file mode 100644 index 00000000..a38236b9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761749001761.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761749278409.png b/static/docs_imagem/tagoio/rounded-image-1761749278409.png new file mode 100644 index 00000000..bec6c355 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761749278409.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1761749322927.png b/static/docs_imagem/tagoio/rounded-image-1761749322927.png new file mode 100644 index 00000000..8330b234 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1761749322927.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762263403092.png b/static/docs_imagem/tagoio/rounded-image-1762263403092.png new file mode 100644 index 00000000..d3741f81 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762263403092.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762263701444.png b/static/docs_imagem/tagoio/rounded-image-1762263701444.png new file mode 100644 index 00000000..d1f4f84f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762263701444.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762263846752.png b/static/docs_imagem/tagoio/rounded-image-1762263846752.png new file mode 100644 index 00000000..de828d40 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762263846752.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762432112336.png b/static/docs_imagem/tagoio/rounded-image-1762432112336.png new file mode 100644 index 00000000..042443a9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762432112336.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762433245481.png b/static/docs_imagem/tagoio/rounded-image-1762433245481.png new file mode 100644 index 00000000..12e67c5d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762433245481.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762437763780.png b/static/docs_imagem/tagoio/rounded-image-1762437763780.png new file mode 100644 index 00000000..31e27ca2 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762437763780.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762438126165.png b/static/docs_imagem/tagoio/rounded-image-1762438126165.png new file mode 100644 index 00000000..c8a77008 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762438126165.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762438254444.png b/static/docs_imagem/tagoio/rounded-image-1762438254444.png new file mode 100644 index 00000000..64ded412 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762438254444.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762438341819.png b/static/docs_imagem/tagoio/rounded-image-1762438341819.png new file mode 100644 index 00000000..8aebb099 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762438341819.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762440792183.png b/static/docs_imagem/tagoio/rounded-image-1762440792183.png new file mode 100644 index 00000000..08910f03 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762440792183.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762440999827.png b/static/docs_imagem/tagoio/rounded-image-1762440999827.png new file mode 100644 index 00000000..76315c2d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762440999827.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441089626.png b/static/docs_imagem/tagoio/rounded-image-1762441089626.png new file mode 100644 index 00000000..ce485c71 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441089626.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441177206.png b/static/docs_imagem/tagoio/rounded-image-1762441177206.png new file mode 100644 index 00000000..b48829fc Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441177206.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441267639.png b/static/docs_imagem/tagoio/rounded-image-1762441267639.png new file mode 100644 index 00000000..57c04e5c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441267639.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441353390.png b/static/docs_imagem/tagoio/rounded-image-1762441353390.png new file mode 100644 index 00000000..3237064e Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441353390.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441468085.png b/static/docs_imagem/tagoio/rounded-image-1762441468085.png new file mode 100644 index 00000000..2ef10ce9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441468085.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441561759.png b/static/docs_imagem/tagoio/rounded-image-1762441561759.png new file mode 100644 index 00000000..2a1f7e92 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441561759.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441641103.png b/static/docs_imagem/tagoio/rounded-image-1762441641103.png new file mode 100644 index 00000000..3912ca1b Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441641103.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762441866641.png b/static/docs_imagem/tagoio/rounded-image-1762441866641.png new file mode 100644 index 00000000..4bde0648 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762441866641.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1762442041853.png b/static/docs_imagem/tagoio/rounded-image-1762442041853.png new file mode 100644 index 00000000..b52def5e Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1762442041853.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764012455142.png b/static/docs_imagem/tagoio/rounded-image-1764012455142.png new file mode 100644 index 00000000..e427341b Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764012455142.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764600146285.png b/static/docs_imagem/tagoio/rounded-image-1764600146285.png new file mode 100644 index 00000000..84bf05da Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764600146285.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764602658282.png b/static/docs_imagem/tagoio/rounded-image-1764602658282.png new file mode 100644 index 00000000..898d07e9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764602658282.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764604280634.png b/static/docs_imagem/tagoio/rounded-image-1764604280634.png new file mode 100644 index 00000000..c4cc84e6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764604280634.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764605013109.png b/static/docs_imagem/tagoio/rounded-image-1764605013109.png new file mode 100644 index 00000000..70c3392e Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764605013109.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764605320147.png b/static/docs_imagem/tagoio/rounded-image-1764605320147.png new file mode 100644 index 00000000..8425b7ac Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764605320147.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764610801394.png b/static/docs_imagem/tagoio/rounded-image-1764610801394.png new file mode 100644 index 00000000..17d214fe Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764610801394.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764611068050.png b/static/docs_imagem/tagoio/rounded-image-1764611068050.png new file mode 100644 index 00000000..f7020a36 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764611068050.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764611428517.png b/static/docs_imagem/tagoio/rounded-image-1764611428517.png new file mode 100644 index 00000000..3b6734b5 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764611428517.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1764772930690.png b/static/docs_imagem/tagoio/rounded-image-1764772930690.png new file mode 100644 index 00000000..aa23b9ff Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1764772930690.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765199046181.png b/static/docs_imagem/tagoio/rounded-image-1765199046181.png new file mode 100644 index 00000000..d5b7bbad Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765199046181.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765199260734.png b/static/docs_imagem/tagoio/rounded-image-1765199260734.png new file mode 100644 index 00000000..3f6aab75 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765199260734.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765199355157.png b/static/docs_imagem/tagoio/rounded-image-1765199355157.png new file mode 100644 index 00000000..0feaf2c7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765199355157.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765199766266.png b/static/docs_imagem/tagoio/rounded-image-1765199766266.png new file mode 100644 index 00000000..a013aacb Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765199766266.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765201391949.png b/static/docs_imagem/tagoio/rounded-image-1765201391949.png new file mode 100644 index 00000000..79585b37 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765201391949.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765201662687.png b/static/docs_imagem/tagoio/rounded-image-1765201662687.png new file mode 100644 index 00000000..0d4b5905 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765201662687.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765201715662.png b/static/docs_imagem/tagoio/rounded-image-1765201715662.png new file mode 100644 index 00000000..4d2ad5b0 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765201715662.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765391012273.png b/static/docs_imagem/tagoio/rounded-image-1765391012273.png new file mode 100644 index 00000000..534a112c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765391012273.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765391484647.png b/static/docs_imagem/tagoio/rounded-image-1765391484647.png new file mode 100644 index 00000000..aeb91131 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765391484647.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765392749974.png b/static/docs_imagem/tagoio/rounded-image-1765392749974.png new file mode 100644 index 00000000..1d9d55e7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765392749974.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765393546195.png b/static/docs_imagem/tagoio/rounded-image-1765393546195.png new file mode 100644 index 00000000..373ad315 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765393546195.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765546206780.png b/static/docs_imagem/tagoio/rounded-image-1765546206780.png new file mode 100644 index 00000000..7d14c1a9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765546206780.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765546342632.png b/static/docs_imagem/tagoio/rounded-image-1765546342632.png new file mode 100644 index 00000000..f2d34257 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765546342632.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765546532507.png b/static/docs_imagem/tagoio/rounded-image-1765546532507.png new file mode 100644 index 00000000..07ca49c6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765546532507.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765546565836.png b/static/docs_imagem/tagoio/rounded-image-1765546565836.png new file mode 100644 index 00000000..2b6318e6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765546565836.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765548629176.png b/static/docs_imagem/tagoio/rounded-image-1765548629176.png new file mode 100644 index 00000000..91a4e23c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765548629176.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765548850873.png b/static/docs_imagem/tagoio/rounded-image-1765548850873.png new file mode 100644 index 00000000..246622ba Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765548850873.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765548941649.png b/static/docs_imagem/tagoio/rounded-image-1765548941649.png new file mode 100644 index 00000000..74bae31d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765548941649.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1765563420353.png b/static/docs_imagem/tagoio/rounded-image-1765563420353.png new file mode 100644 index 00000000..16d8f4b7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1765563420353.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766775464345.png b/static/docs_imagem/tagoio/rounded-image-1766775464345.png new file mode 100644 index 00000000..cbd8402f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766775464345.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766775731728.png b/static/docs_imagem/tagoio/rounded-image-1766775731728.png new file mode 100644 index 00000000..dfcaf967 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766775731728.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766775773235.png b/static/docs_imagem/tagoio/rounded-image-1766775773235.png new file mode 100644 index 00000000..67f02a1a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766775773235.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766775810232.png b/static/docs_imagem/tagoio/rounded-image-1766775810232.png new file mode 100644 index 00000000..95bebb1d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766775810232.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766775932693.png b/static/docs_imagem/tagoio/rounded-image-1766775932693.png new file mode 100644 index 00000000..9f0b891d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766775932693.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766777720645.png b/static/docs_imagem/tagoio/rounded-image-1766777720645.png new file mode 100644 index 00000000..f97603e3 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766777720645.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1766777978480.png b/static/docs_imagem/tagoio/rounded-image-1766777978480.png new file mode 100644 index 00000000..d736c163 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1766777978480.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767013456603.png b/static/docs_imagem/tagoio/rounded-image-1767013456603.png new file mode 100644 index 00000000..df16b089 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767013456603.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767013673736.png b/static/docs_imagem/tagoio/rounded-image-1767013673736.png new file mode 100644 index 00000000..b9a6fe75 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767013673736.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014195631.png b/static/docs_imagem/tagoio/rounded-image-1767014195631.png new file mode 100644 index 00000000..c3acf6fe Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014195631.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014262674.png b/static/docs_imagem/tagoio/rounded-image-1767014262674.png new file mode 100644 index 00000000..bf7e8745 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014262674.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014361018.png b/static/docs_imagem/tagoio/rounded-image-1767014361018.png new file mode 100644 index 00000000..d0e12b11 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014361018.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014455919.png b/static/docs_imagem/tagoio/rounded-image-1767014455919.png new file mode 100644 index 00000000..bf8c2d5c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014455919.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014507673.png b/static/docs_imagem/tagoio/rounded-image-1767014507673.png new file mode 100644 index 00000000..4ad43da5 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014507673.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014557842.png b/static/docs_imagem/tagoio/rounded-image-1767014557842.png new file mode 100644 index 00000000..984d36e8 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014557842.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014631018.png b/static/docs_imagem/tagoio/rounded-image-1767014631018.png new file mode 100644 index 00000000..34d4dc2c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014631018.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014751312.png b/static/docs_imagem/tagoio/rounded-image-1767014751312.png new file mode 100644 index 00000000..d583a5ad Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014751312.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767014904194.png b/static/docs_imagem/tagoio/rounded-image-1767014904194.png new file mode 100644 index 00000000..e76611eb Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767014904194.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767016336359.png b/static/docs_imagem/tagoio/rounded-image-1767016336359.png new file mode 100644 index 00000000..a31deea3 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767016336359.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767016364577.png b/static/docs_imagem/tagoio/rounded-image-1767016364577.png new file mode 100644 index 00000000..6fd74b3b Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767016364577.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767016482525.png b/static/docs_imagem/tagoio/rounded-image-1767016482525.png new file mode 100644 index 00000000..273a8731 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767016482525.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767016776767.png b/static/docs_imagem/tagoio/rounded-image-1767016776767.png new file mode 100644 index 00000000..0915cf55 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767016776767.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767018081996.png b/static/docs_imagem/tagoio/rounded-image-1767018081996.png new file mode 100644 index 00000000..1be314a9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767018081996.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767018166748.png b/static/docs_imagem/tagoio/rounded-image-1767018166748.png new file mode 100644 index 00000000..7a3fd01e Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767018166748.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767028703029.png b/static/docs_imagem/tagoio/rounded-image-1767028703029.png new file mode 100644 index 00000000..b5ecfdc8 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767028703029.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767030524609.png b/static/docs_imagem/tagoio/rounded-image-1767030524609.png new file mode 100644 index 00000000..ffc9761b Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767030524609.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767033430352.png b/static/docs_imagem/tagoio/rounded-image-1767033430352.png new file mode 100644 index 00000000..386aa971 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767033430352.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767033964525.png b/static/docs_imagem/tagoio/rounded-image-1767033964525.png new file mode 100644 index 00000000..95ea5fa2 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767033964525.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767034014646.png b/static/docs_imagem/tagoio/rounded-image-1767034014646.png new file mode 100644 index 00000000..2135ba35 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767034014646.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767725721851.png b/static/docs_imagem/tagoio/rounded-image-1767725721851.png new file mode 100644 index 00000000..3eb67331 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767725721851.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767726076769.png b/static/docs_imagem/tagoio/rounded-image-1767726076769.png new file mode 100644 index 00000000..144bd5f7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767726076769.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767726141891.png b/static/docs_imagem/tagoio/rounded-image-1767726141891.png new file mode 100644 index 00000000..9e3d9f08 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767726141891.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767727513332.png b/static/docs_imagem/tagoio/rounded-image-1767727513332.png new file mode 100644 index 00000000..a4cbc5c6 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767727513332.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767727705660.png b/static/docs_imagem/tagoio/rounded-image-1767727705660.png new file mode 100644 index 00000000..034102f9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767727705660.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767727794882.png b/static/docs_imagem/tagoio/rounded-image-1767727794882.png new file mode 100644 index 00000000..7d01688a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767727794882.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767727863200.png b/static/docs_imagem/tagoio/rounded-image-1767727863200.png new file mode 100644 index 00000000..4584f641 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767727863200.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767728352363.png b/static/docs_imagem/tagoio/rounded-image-1767728352363.png new file mode 100644 index 00000000..a07c31a3 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767728352363.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767728631182.png b/static/docs_imagem/tagoio/rounded-image-1767728631182.png new file mode 100644 index 00000000..a7e3530a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767728631182.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767728781271.png b/static/docs_imagem/tagoio/rounded-image-1767728781271.png new file mode 100644 index 00000000..9eecb5ab Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767728781271.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767728974371.png b/static/docs_imagem/tagoio/rounded-image-1767728974371.png new file mode 100644 index 00000000..c03b06c4 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767728974371.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1767729055179.png b/static/docs_imagem/tagoio/rounded-image-1767729055179.png new file mode 100644 index 00000000..9f57aed4 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1767729055179.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1768488628525.png b/static/docs_imagem/tagoio/rounded-image-1768488628525.png new file mode 100644 index 00000000..ba685a26 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1768488628525.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1768488678984.png b/static/docs_imagem/tagoio/rounded-image-1768488678984.png new file mode 100644 index 00000000..6695b2d5 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1768488678984.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1768488814377.png b/static/docs_imagem/tagoio/rounded-image-1768488814377.png new file mode 100644 index 00000000..8cbc8d75 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1768488814377.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769086347748.png b/static/docs_imagem/tagoio/rounded-image-1769086347748.png new file mode 100644 index 00000000..315be238 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769086347748.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769086495362.png b/static/docs_imagem/tagoio/rounded-image-1769086495362.png new file mode 100644 index 00000000..1fe7d924 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769086495362.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769086543434.png b/static/docs_imagem/tagoio/rounded-image-1769086543434.png new file mode 100644 index 00000000..46bfbe83 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769086543434.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769101024685.png b/static/docs_imagem/tagoio/rounded-image-1769101024685.png new file mode 100644 index 00000000..e1d0252f Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769101024685.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769101086998.png b/static/docs_imagem/tagoio/rounded-image-1769101086998.png new file mode 100644 index 00000000..8141710c Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769101086998.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769101281198.png b/static/docs_imagem/tagoio/rounded-image-1769101281198.png new file mode 100644 index 00000000..c057b5c2 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769101281198.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769101996090.png b/static/docs_imagem/tagoio/rounded-image-1769101996090.png new file mode 100644 index 00000000..bd0361cf Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769101996090.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769102191287.png b/static/docs_imagem/tagoio/rounded-image-1769102191287.png new file mode 100644 index 00000000..e453489d Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769102191287.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769102832066.png b/static/docs_imagem/tagoio/rounded-image-1769102832066.png new file mode 100644 index 00000000..9c954612 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769102832066.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769102866603.png b/static/docs_imagem/tagoio/rounded-image-1769102866603.png new file mode 100644 index 00000000..c85f24ce Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769102866603.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769102998326.png b/static/docs_imagem/tagoio/rounded-image-1769102998326.png new file mode 100644 index 00000000..c137b793 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769102998326.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103195000.png b/static/docs_imagem/tagoio/rounded-image-1769103195000.png new file mode 100644 index 00000000..22882a81 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103195000.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103294865.png b/static/docs_imagem/tagoio/rounded-image-1769103294865.png new file mode 100644 index 00000000..a4b58705 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103294865.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103607957.png b/static/docs_imagem/tagoio/rounded-image-1769103607957.png new file mode 100644 index 00000000..68668ec9 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103607957.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103706398.png b/static/docs_imagem/tagoio/rounded-image-1769103706398.png new file mode 100644 index 00000000..89ae11e5 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103706398.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103742011.png b/static/docs_imagem/tagoio/rounded-image-1769103742011.png new file mode 100644 index 00000000..5daad966 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103742011.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103781795.png b/static/docs_imagem/tagoio/rounded-image-1769103781795.png new file mode 100644 index 00000000..464829a7 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103781795.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103890139.png b/static/docs_imagem/tagoio/rounded-image-1769103890139.png new file mode 100644 index 00000000..7d0d0613 Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103890139.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769103991697.png b/static/docs_imagem/tagoio/rounded-image-1769103991697.png new file mode 100644 index 00000000..45ed026a Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769103991697.png differ diff --git a/static/docs_imagem/tagoio/rounded-image-1769104184640.png b/static/docs_imagem/tagoio/rounded-image-1769104184640.png new file mode 100644 index 00000000..869ba6ba Binary files /dev/null and b/static/docs_imagem/tagoio/rounded-image-1769104184640.png differ diff --git a/static/docs_imagem/tagoio/router-3.png b/static/docs_imagem/tagoio/router-3.png deleted file mode 100644 index 4ca1b3be..00000000 Binary files a/static/docs_imagem/tagoio/router-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/router-4.png b/static/docs_imagem/tagoio/router-4.png deleted file mode 100644 index 86f7ad0d..00000000 Binary files a/static/docs_imagem/tagoio/router-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/rpm_list_advanced_statistics.png b/static/docs_imagem/tagoio/rpm_list_advanced_statistics.png deleted file mode 100644 index 1e118b39..00000000 Binary files a/static/docs_imagem/tagoio/rpm_list_advanced_statistics.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/script-editor-2.png b/static/docs_imagem/tagoio/script-editor-2.png deleted file mode 100644 index b2c886a1..00000000 Binary files a/static/docs_imagem/tagoio/script-editor-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/semi-donut-widget-3.gif b/static/docs_imagem/tagoio/semi-donut-widget-3.gif deleted file mode 100644 index 2687f93e..00000000 Binary files a/static/docs_imagem/tagoio/semi-donut-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/semi-pie-widget-3.gif b/static/docs_imagem/tagoio/semi-pie-widget-3.gif deleted file mode 100644 index ff2e4de6..00000000 Binary files a/static/docs_imagem/tagoio/semi-pie-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/senra-network-4.png b/static/docs_imagem/tagoio/senra-network-4.png deleted file mode 100644 index b39fc24d..00000000 Binary files a/static/docs_imagem/tagoio/senra-network-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sensit-with-sigfox-2.png b/static/docs_imagem/tagoio/sensit-with-sigfox-2.png deleted file mode 100644 index 823c23f6..00000000 Binary files a/static/docs_imagem/tagoio/sensit-with-sigfox-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sensit-with-sigfox-3.png b/static/docs_imagem/tagoio/sensit-with-sigfox-3.png deleted file mode 100644 index b517a121..00000000 Binary files a/static/docs_imagem/tagoio/sensit-with-sigfox-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sensit-with-sigfox-4.png b/static/docs_imagem/tagoio/sensit-with-sigfox-4.png deleted file mode 100644 index 0e65ad25..00000000 Binary files a/static/docs_imagem/tagoio/sensit-with-sigfox-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-2.png b/static/docs_imagem/tagoio/sigfox-2.png deleted file mode 100644 index cfe28e24..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-4.png b/static/docs_imagem/tagoio/sigfox-4.png deleted file mode 100644 index bb894f01..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-downlink-2.png b/static/docs_imagem/tagoio/sigfox-downlink-2.png deleted file mode 100644 index e2531c3c..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-downlink-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-downlink-3.png b/static/docs_imagem/tagoio/sigfox-downlink-3.png deleted file mode 100644 index cc301754..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-downlink-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-downlink-4.png b/static/docs_imagem/tagoio/sigfox-downlink-4.png deleted file mode 100644 index 5b1c9927..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-downlink-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/sigfox-downlink-5.png b/static/docs_imagem/tagoio/sigfox-downlink-5.png deleted file mode 100644 index 636969d7..00000000 Binary files a/static/docs_imagem/tagoio/sigfox-downlink-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/simulator-data-stream-3.png b/static/docs_imagem/tagoio/simulator-data-stream-3.png deleted file mode 100644 index 28891b01..00000000 Binary files a/static/docs_imagem/tagoio/simulator-data-stream-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/single-sign-on-sso-2.png b/static/docs_imagem/tagoio/single-sign-on-sso-2.png deleted file mode 100644 index ccf746a2..00000000 Binary files a/static/docs_imagem/tagoio/single-sign-on-sso-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/solid-widget-3.gif b/static/docs_imagem/tagoio/solid-widget-3.gif deleted file mode 100644 index b270ad85..00000000 Binary files a/static/docs_imagem/tagoio/solid-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/static-table-widget-4.png b/static/docs_imagem/tagoio/static-table-widget-4.png deleted file mode 100644 index 419e719a..00000000 Binary files a/static/docs_imagem/tagoio/static-table-widget-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/static-table-widget-5.gif b/static/docs_imagem/tagoio/static-table-widget-5.gif deleted file mode 100644 index fda9a603..00000000 Binary files a/static/docs_imagem/tagoio/static-table-widget-5.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/step-button-widget-3.gif b/static/docs_imagem/tagoio/step-button-widget-3.gif deleted file mode 100644 index a4cde4e4..00000000 Binary files a/static/docs_imagem/tagoio/step-button-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/tagoIO_ttn-WUw.png b/static/docs_imagem/tagoio/tagoIO_ttn-WUw.png deleted file mode 100644 index 16a5d814..00000000 Binary files a/static/docs_imagem/tagoio/tagoIO_ttn-WUw.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/the-things-network-lorawan-2.png b/static/docs_imagem/tagoio/the-things-network-lorawan-2.png deleted file mode 100644 index a43255c5..00000000 Binary files a/static/docs_imagem/tagoio/the-things-network-lorawan-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/the-things-network-lorawan-3.png&blockId=edbsn8d9972ac801485733a54ba20d39542298ebcff40d27d72339b0702fcefb4948e&zgId=edbsn631a5119ab7b66930d9988a5e8622b55&mode=view b/static/docs_imagem/tagoio/the-things-network-lorawan-3.png&blockId=edbsn8d9972ac801485733a54ba20d39542298ebcff40d27d72339b0702fcefb4948e&zgId=edbsn631a5119ab7b66930d9988a5e8622b55&mode=view deleted file mode 100644 index 48447d62..00000000 Binary files a/static/docs_imagem/tagoio/the-things-network-lorawan-3.png&blockId=edbsn8d9972ac801485733a54ba20d39542298ebcff40d27d72339b0702fcefb4948e&zgId=edbsn631a5119ab7b66930d9988a5e8622b55&mode=view and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png b/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png deleted file mode 100644 index 617edb9d..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-4.png b/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-4.png deleted file mode 100644 index 0ab098df..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-5.png b/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-5.png deleted file mode 100644 index b4b9f777..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-6.png b/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-6.png deleted file mode 100644 index 14e6267d..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra-xkit-for-sigfox-6.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra_Dash-7pM.png b/static/docs_imagem/tagoio/thinxtra_Dash-7pM.png deleted file mode 100644 index 0f2de374..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra_Dash-7pM.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/thinxtra_selection_tagoio-PIU.png b/static/docs_imagem/tagoio/thinxtra_selection_tagoio-PIU.png deleted file mode 100644 index 0f2de374..00000000 Binary files a/static/docs_imagem/tagoio/thinxtra_selection_tagoio-PIU.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/tile-widget-3.gif b/static/docs_imagem/tagoio/tile-widget-3.gif deleted file mode 100644 index 88153e93..00000000 Binary files a/static/docs_imagem/tagoio/tile-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/tile-widget-4.png b/static/docs_imagem/tagoio/tile-widget-4.png deleted file mode 100644 index b5819fc7..00000000 Binary files a/static/docs_imagem/tagoio/tile-widget-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/touchtag-lorawan-everynet-3.png b/static/docs_imagem/tagoio/touchtag-lorawan-everynet-3.png deleted file mode 100644 index 736b8187..00000000 Binary files a/static/docs_imagem/tagoio/touchtag-lorawan-everynet-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/trigger-by-mqtt-topic-3.png b/static/docs_imagem/tagoio/trigger-by-mqtt-topic-3.png deleted file mode 100644 index 6a3e68ab..00000000 Binary files a/static/docs_imagem/tagoio/trigger-by-mqtt-topic-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/trigger-by-schedule-3.png b/static/docs_imagem/tagoio/trigger-by-schedule-3.png deleted file mode 100644 index 9a714394..00000000 Binary files a/static/docs_imagem/tagoio/trigger-by-schedule-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/trigger-by-schedule-4.png b/static/docs_imagem/tagoio/trigger-by-schedule-4.png deleted file mode 100644 index cbb5dbf3..00000000 Binary files a/static/docs_imagem/tagoio/trigger-by-schedule-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/trigger-by-variable-3.png b/static/docs_imagem/tagoio/trigger-by-variable-3.png deleted file mode 100644 index 0daf6c73..00000000 Binary files a/static/docs_imagem/tagoio/trigger-by-variable-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/trigger-by-variable-4.png b/static/docs_imagem/tagoio/trigger-by-variable-4.png deleted file mode 100644 index 5e32149c..00000000 Binary files a/static/docs_imagem/tagoio/trigger-by-variable-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/two-factor-authentication-2fa-2.png b/static/docs_imagem/tagoio/two-factor-authentication-2fa-2.png deleted file mode 100644 index b562c7cb..00000000 Binary files a/static/docs_imagem/tagoio/two-factor-authentication-2fa-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/two-factor-authentication-2fa-3.gif b/static/docs_imagem/tagoio/two-factor-authentication-2fa-3.gif deleted file mode 100644 index 5c8b9466..00000000 Binary files a/static/docs_imagem/tagoio/two-factor-authentication-2fa-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/uploading-files-2.png b/static/docs_imagem/tagoio/uploading-files-2.png deleted file mode 100644 index 7c08ae9f..00000000 Binary files a/static/docs_imagem/tagoio/uploading-files-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/uploading-files-3.png b/static/docs_imagem/tagoio/uploading-files-3.png deleted file mode 100644 index 4a2744f3..00000000 Binary files a/static/docs_imagem/tagoio/uploading-files-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/uploading-files-4.png b/static/docs_imagem/tagoio/uploading-files-4.png deleted file mode 100644 index 64ee9d35..00000000 Binary files a/static/docs_imagem/tagoio/uploading-files-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/uploading-files-5.png b/static/docs_imagem/tagoio/uploading-files-5.png deleted file mode 100644 index 4c3ba7ab..00000000 Binary files a/static/docs_imagem/tagoio/uploading-files-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/user-management-2.png b/static/docs_imagem/tagoio/user-management-2.png deleted file mode 100644 index 1ce28c1c..00000000 Binary files a/static/docs_imagem/tagoio/user-management-2.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/using-dictionaries-multi-language-3.png b/static/docs_imagem/tagoio/using-dictionaries-multi-language-3.png deleted file mode 100644 index df2b8242..00000000 Binary files a/static/docs_imagem/tagoio/using-dictionaries-multi-language-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/using-dictionaries-multi-language-4.png b/static/docs_imagem/tagoio/using-dictionaries-multi-language-4.png deleted file mode 100644 index 84f02001..00000000 Binary files a/static/docs_imagem/tagoio/using-dictionaries-multi-language-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/using-dictionaries-multi-language-5.png b/static/docs_imagem/tagoio/using-dictionaries-multi-language-5.png deleted file mode 100644 index fe1ca4e6..00000000 Binary files a/static/docs_imagem/tagoio/using-dictionaries-multi-language-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/using-dictionaries-multi-language-6.jpg b/static/docs_imagem/tagoio/using-dictionaries-multi-language-6.jpg deleted file mode 100644 index 013759dd..00000000 Binary files a/static/docs_imagem/tagoio/using-dictionaries-multi-language-6.jpg and /dev/null differ diff --git a/static/docs_imagem/tagoio/using-dictionaries-multi-language-7.png b/static/docs_imagem/tagoio/using-dictionaries-multi-language-7.png deleted file mode 100644 index d5485b62..00000000 Binary files a/static/docs_imagem/tagoio/using-dictionaries-multi-language-7.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/vertical-column-widget-4.gif b/static/docs_imagem/tagoio/vertical-column-widget-4.gif deleted file mode 100644 index 85817363..00000000 Binary files a/static/docs_imagem/tagoio/vertical-column-widget-4.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/vertical-column-widget-5.png b/static/docs_imagem/tagoio/vertical-column-widget-5.png deleted file mode 100644 index 1bcc7c32..00000000 Binary files a/static/docs_imagem/tagoio/vertical-column-widget-5.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/vertical-column-widget-6.gif b/static/docs_imagem/tagoio/vertical-column-widget-6.gif deleted file mode 100644 index 157b0449..00000000 Binary files a/static/docs_imagem/tagoio/vertical-column-widget-6.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/vu-meter-widget-3.gif b/static/docs_imagem/tagoio/vu-meter-widget-3.gif deleted file mode 100644 index b7610cb2..00000000 Binary files a/static/docs_imagem/tagoio/vu-meter-widget-3.gif and /dev/null differ diff --git a/static/docs_imagem/tagoio/widget-header-3.png b/static/docs_imagem/tagoio/widget-header-3.png deleted file mode 100644 index 4dc49994..00000000 Binary files a/static/docs_imagem/tagoio/widget-header-3.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/widget-header-4.png b/static/docs_imagem/tagoio/widget-header-4.png deleted file mode 100644 index 52f0bef8..00000000 Binary files a/static/docs_imagem/tagoio/widget-header-4.png and /dev/null differ diff --git a/static/docs_imagem/tagoio/widgetcreation.gif b/static/docs_imagem/tagoio/widgetcreation.gif new file mode 100644 index 00000000..73f39906 Binary files /dev/null and b/static/docs_imagem/tagoio/widgetcreation.gif differ diff --git a/static/docs_imagem/tagoio/xkit_pinout-Sgw.png b/static/docs_imagem/tagoio/xkit_pinout-Sgw.png deleted file mode 100644 index 4cdbe84e..00000000 Binary files a/static/docs_imagem/tagoio/xkit_pinout-Sgw.png and /dev/null differ