diff --git a/doc/content/integrations/cloud-integrations/azure-iot-central/device-twin.md b/doc/content/integrations/cloud-integrations/azure-iot-central/device-twin.md index ab6597e1e8..04306206a7 100644 --- a/doc/content/integrations/cloud-integrations/azure-iot-central/device-twin.md +++ b/doc/content/integrations/cloud-integrations/azure-iot-central/device-twin.md @@ -87,7 +87,7 @@ An example of this property as unmodeled data would look as follows: > `frm-payload` is the service name for the service which derives the end device location from the decoded payload. -- `serviceData` - Object mapping between the service (name) and the service data reported by that service. Used by integrations such as [LoRa Cloud]({{< ref "/integrations/other-integrations/lora-cloud" >}}). +- `serviceData` - Object mapping between the service (name) and the service data reported by that service. Used by third-party integrations. - `decodedPayload` - Decoded payload of the uplink messages, which is generated using the [Payload Formatters]({{< ref "/integrations/payload-formatters" >}}). An example of this property as unmodeled data would look as follows: diff --git a/doc/content/integrations/cloud-integrations/ttnmapper/_index.md b/doc/content/integrations/cloud-integrations/ttnmapper/_index.md index 9f242073af..f7aca37750 100644 --- a/doc/content/integrations/cloud-integrations/ttnmapper/_index.md +++ b/doc/content/integrations/cloud-integrations/ttnmapper/_index.md @@ -21,8 +21,6 @@ Your end device can be sending its GPS coordinates in an uplink message as part - If your end device is sending data in Cayenne LPP format, choose [Cayenne LPP payload formatter](({{< ref "/integrations/payload-formatters/cayenne" >}})) in your device's settings on {{% tts %}}. - Otherwise, create a custom [JavaScript payload formatter]({{< ref "/integrations/payload-formatters/javascript" >}}). This formatter will have to contain fields `latitude`, `longitude` and `altitude`. If possible, `hdop`, `accuracy` or `sats` fields should also be contained. - - The next step is to instantiate the **TTN Mapper** [Webhook template]({{< ref "/integrations/webhooks/webhook-templates" >}}). diff --git a/doc/content/integrations/other-integrations/lora-cloud/_index.md b/doc/content/integrations/other-integrations/lora-cloud/_index.md deleted file mode 100644 index 4b34e63674..0000000000 --- a/doc/content/integrations/other-integrations/lora-cloud/_index.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: "LoRa Cloud" -description: "" -weight: 60 -aliases: [/integrations/lora-cloud] ---- - -[LoRa Cloud™](https://www.loracloud.com/) platform offers value-added APIs that enable simple solutions for common tasks related to LoRaWAN® networks and LoRa-based devices. {{% tts %}} supports integrations with [LoRa Cloud Modem Services]({{< ref "/integrations/other-integrations/lora-cloud/modem-services" >}}) and [LoRa Cloud Geolocation Services]({{< ref "/integrations/other-integrations/lora-cloud/geolocation-services" >}}). - - - -The [LoRa Edge™ LR1110](https://www.semtech.com/products/wireless-rf/lora-edge/) solution was used for writing this guide. - -This device is running the LoRa Basics Modem-E Firmware and the LoRa Basics Modem-E Demo Application, which provide the device with enough capabilities to perform operations that are of interest in this guide, like WiFi and GNSS assisted scanning. To install the aforementioned firmware and the demo application, follow [this guide](https://lora-developers.semtech.com/learning-center/hands-on-labs/build-end-to-end-solution-using-lorawan-and-loraedge/install-nucleo-and-lr1110-software/). - -The device is claimed using the [LoRa Cloud Device Join Service](https://www.loracloud.com/documentation/join_service?url=index.html). That operation is out of the scope of this guide and {{% tts %}} documentation in general, but you can find the detailed documentation on how to claim your device at [Semtech's Learning Center site](https://lora-developers.semtech.com/learning-center/hands-on-labs/build-end-to-end-solution-using-lorawan-and-loraedge/claim-your-device-on-the-lora-cloud-portal/). - -In this guide, we assume you already [added the device]({{< ref "/hardware/devices/adding-devices" >}}) in {{% tts %}} Console. Please keep in mind that in case of using the LoRa Cloud Device Join Service for claiming, you have to tick the **External Join Server** box when adding the device in {{% tts %}} Console, as described [here]({{< ref "/hardware/devices/adding-devices#manually-create-end-device" >}}). - -Keep reading the subtopics in the **left menu** to learn how to integrate and make use of LoRa Cloud features. diff --git a/doc/content/integrations/other-integrations/lora-cloud/add-device.png b/doc/content/integrations/other-integrations/lora-cloud/add-device.png deleted file mode 100644 index 5670d74171..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/add-device.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/copy-token.png b/doc/content/integrations/other-integrations/lora-cloud/copy-token.png deleted file mode 100644 index 5bc2c99c91..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/copy-token.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/create-token.png b/doc/content/integrations/other-integrations/lora-cloud/create-token.png deleted file mode 100644 index 2a61b86447..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/create-token.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/full-info.png b/doc/content/integrations/other-integrations/lora-cloud/full-info.png deleted file mode 100644 index 0028abd85a..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/full-info.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/geolocation-services.md b/doc/content/integrations/other-integrations/lora-cloud/geolocation-services.md deleted file mode 100644 index b469b8255d..0000000000 --- a/doc/content/integrations/other-integrations/lora-cloud/geolocation-services.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: "LoRa Cloud Geolocation Services" -description: "" -weight: 2 -aliases: [/integrations/lora-cloud/geolocation-services, /integrations/lora-cloud/geolocation/] ---- - -[LoRa Cloud Geolocation Services](https://www.loracloud.com/portal/geolocation/home) provides simple JSON web APIs that can be easily integrated with a LoRaWAN network or application server to enable estimating the location of LoRa-based devices. - - - -In general, LoRa allows locating devices withing approximately 50m, without the need for a geolocation hardware module and no extra power consumption. Instead, the RSSI, SNR and TOA metadata that are being sent as part of your device's LoRa radio frames are used to estimate the location of your device. If your device can perform WiFi scans, scanning results can also be used to estimate your device's location. This yields a significant cost reduction compared to GPS. - -{{< note >}} Keep in mind that TOA is available only in metadata of gateways that have appropriate high-resolution time-stamping features. Therefore, your gateway needs to support this feature in order for you to be able to use TOA-based geolocation features. {{}} - -Also, LoRa Cloud Geolocation integration allows estimating the location of LR1110-based devices with transceiver firmware from their GNSS scans. - -Three query types are supported in scope of this integration and will be demonstrated below: - -- [LoRa TOA/RSSI](https://www.loracloud.com/documentation/geolocation?url=v3.html) - allows computing the location estimates using TOA and/or RSSI information from a single or multiple LoRa frames (for all LoRa devices) -- [GNSS](https://www.loracloud.com/documentation/geolocation?url=gnss.html) - location estimates are computed from the information contained in the GNSS scan result messages (NAV messages) (for LR1110 transceiver-based devices only) -- [TOA/WiFi](https://www.loracloud.com/documentation/geolocation?url=v2.html#singleframe-wi-fi-tdoa-request) - the initial device location estimation is performed using the scanned WiFi access points, but if this estimation is not valid, another estimation is performed based on TOA metadata from device's LoRa radio frames (for all LoRa devices capable of performing WiFi scans) - -{{< warning >}} It is important to know that you can obtain the location estimates using LoRa Cloud Geolocation LoRa TOA/RSSI query only if the uplink messages sent by your end device are picked up by at least 3 LoRaWAN gateways. If this is not the case, you will see no errors in {{% tts %}} Console, but you will not see the `Location solved` message containing the location estimation results either. {{}} - -The location of your gateway has to be publicly available for this integration, as it participates in the process of computing the end device location. This is disabled in {{% tts %}} by default, because the application (and end device) owner does not have be the one providing the gateway coverage. If you own the gateway, it is safe for you to explicitly allow to publish its location. - -To make the gateway location public, tick the **Gateway location → Public** box when [adding your gateway]({{< ref "/hardware/gateways/concepts/adding-gateways" >}}) in {{% tts %}} Console. - -If your gateway is already added in {{% tts %}} Console, go to your gateway's settings, navigate to the **Location** tab on the left hand menu and tick the **Privacy → Publish location** box. - -{{< note >}} Using Semtech's [Modem-E firmware](https://lora-developers.semtech.com/library/tech-papers-and-guides/understanding-lora-basics-modem-e/) is recommended for LR1110-based devices, hence using the [LoRa Cloud Modem Services integration]({{< ref "/integrations/other-integrations/lora-cloud/modem-services" >}}) instead of LoRa Cloud Geolocation is also recommended. {{}} - -Before proceding with this guide, make sure you have completed the [LoRa Cloud Setup]({{< ref "/integrations/other-integrations/lora-cloud/portal" >}}) guide. - -## Configure Geolocation Integration - -To setup LoRa Cloud Geolocation integration, navigate to your application in {{% tts %}}. - -On the left hand menu, select **Integrations → LoRa Cloud**. Click the **Expand** button next to the **Geolocation services**. - -Next, copy the token you previously created in LoRa Cloud Modem & Geolocation Services portal and paste it in the **Token** field. - -{{< figure src="../copy-token.png" alt="Copy the token from LoRa Cloud" >}} - -Choose the **Query type** depending on the type of data you want to use for estimating the location of your device. As mentioned earlier, you can choose **LoRa TOA/RSSI**, **GNSS** or **TOA/WiFi** query type. - -If you choose **LoRa TOA/RSSI**, you also have an option to enable **Multiframe** location lookups. Multiframe mode allows using the sequence of radio frames (instead of just a single frame) to improve the device's location estimation accuracy. Multiframe mode is reported to be more accurate than averaging multiple location results calculated from several single radio frames. If you choose multiframe mode, you can also set the **Multiframe window size** to tell how many historical messages should be sent as part of the final request, and **Multiframe time window** as the maximum age of considered historical messages. - -The setting for the Server URL points to the LoRa Cloud Modem & Geolocation Services and is set by default. Changing this is unnecessary. - -Finish by clicking the **Set token** button. - -{{< figure src="../paste-token-geolocation.png" alt="LoRa Cloud Geolocation integration" >}} - -## Obtain Location Solutions - -This section will show you how to obtain the location estimates using LoRa® TOA/RSSI, GNSS and TOA/WiFi query types. - -After you obtain the location results, you can further integrate your {{% tts %}} application with other third-party IoT platforms to visualize them, etc. - -### LoRa TOA/RSSI - -At this point, when your LoRa device sends any uplink message and it gets picked up by at least 3 gateways, you will notice the location estimation results present in the `Location solved` message in {{% tts %}} **Live data** tab, as shown below. - -{{< figure src="../toa-rssi.png" alt="LoRa TOA/RSSI location estimate" >}} - -Notice the `Source: LORA_RSSI_GEOLOCATION` which indicates the type of the query you chose for geolocation. - -{{< warning >}} Keep in mind that if your device's uplink message was not picked up by at least 3 gateways, you will not see the Location solved message in {{% tts %}} **Live data** view, but you will not see any errors either. {{}} - -### GNSS - -When your LR1110 transceiver performs a GNSS scan and sends the resulting data in an uplink NAV message, you will see the location estimate present in the `Location solved` message in {{% tts %}} **Live data** tab, as shown below. - -{{< figure src="../gnss.png" alt="GNSS location estimate" >}} - -Notice the `Source: GPS` which indicates the type of the query you chose for geolocation. - -{{< warning >}} For GNSS-based geolocation, the GNSS payload has to be valid. Otherwise, you will see an error similar to `Ignore invalid GNSS message payload: `. This is likely going to happen if you are not using LR1110-based device with transceiver firmware. {{}} - -### TOA/WiFi - -When your LoRa device performs a WiFi scan and sends a resulting uplink message, the payload contains the MAC addresses of WiFi adapters and RSSIs of scanned WiFi networks. You need to decode this payload using the [uplink payload formatter function]({{< ref "/integrations/payload-formatters/javascript" >}}) in a way that the `decoded_payload` object that is a part of the `uplink_message` contains the access point records, like so: - -```js -"decoded_payload": { - "access_points": [ - { - "bssid": "14:60:80:9a:19:58", - "rssi": -20 - }, - { - "bssid": "fc:f5:28:7b:07:e5", - "rssi": -80 - } - ] -} -``` - -If estimating the location based on WiFi access point records cannot be performed, the location will be estimated using the TOA information from LoRa radio metadata and gateway location. In both cases, you will see the location estimate present in the `Location solved` message in {{% tts %}} **Live data** tab, as shown below. - -{{< figure src="../toa-wifi.png" alt="TOA/WiFi location estimate" >}} - -Notice the `Source: WIFI_RSSI_GEOLOCATION` which indicates the type of the query you chose for geolocation. diff --git a/doc/content/integrations/other-integrations/lora-cloud/get-info.png b/doc/content/integrations/other-integrations/lora-cloud/get-info.png deleted file mode 100644 index 3ac8273043..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/get-info.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/gnss-assisted-scan-result.png b/doc/content/integrations/other-integrations/lora-cloud/gnss-assisted-scan-result.png deleted file mode 100644 index 4acf512186..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/gnss-assisted-scan-result.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/gnss.png b/doc/content/integrations/other-integrations/lora-cloud/gnss.png deleted file mode 100644 index b7128fd114..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/gnss.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/modem-services.md b/doc/content/integrations/other-integrations/lora-cloud/modem-services.md deleted file mode 100644 index c6d72392a7..0000000000 --- a/doc/content/integrations/other-integrations/lora-cloud/modem-services.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: "LoRa Cloud Modem Services" -description: "" -weight: 3 -aliases: [/integrations/lora-cloud/modem-services] ---- - -[LoRa Cloud Modem Services](https://www.loracloud.com/portal/device_management/home) complement your device management solution by giving you fine grain control of your LoRaWAN® end devices. It allows to obtain modem status information such as: system status, firmware version, voltage, downlink signal quality and time since last downlink. - - - -LoRa Cloud Modem Services protocol lets you manage common device functionality at the application layer for all LoRa-based devices, and manage geolocation for modem-based devices (like [LoRa Edge LR1110 Solution](https://www.loracloud.com/documentation/device_management?url=overview.html#lora-edge-lr1110-solution)). These services also provide protocols for reliable application data reception from all Semtech's LoRaWAN-compatible devices, with efficient techniques to fight against packet loss. - -In general, LoRa Cloud Modem Services do not interact directly with network servers to retrieve uplinks or schedule downlinks, so it is usually users's responsibility to forward uplinks towards and schedule downlinks from LoRa Cloud as a part of the response. - -However, when it comes to geolocation for modem-based devices, {{% tts %}} integration with LoRa Cloud Modem Services handles this on behalf of the user, i.e. it queries the protocol engine on LoRa Cloud in order to retrieve the response. This way, after the integration is configured and the uplink message containing scanning result is sent from the device, the user only has to monitor results in {{% tts %}}. - -Before proceding with this guide, make sure you have completed the [LoRa Cloud Setup]({{< ref "/integrations/other-integrations/lora-cloud/portal" >}}) guide. - -## Configure LoRa Cloud Modem Services Integration - -To setup LoRa Cloud Modem Services integration, navigate to your application in {{% tts %}}. - -On the left hand menu, select **Integrations → LoRa Cloud**. Click the **Expand** button next to the **Modem Services**. - -Next, copy the token you previously created in LoRa Cloud Modem & Geolocation Services portal and paste it in the **Token** field. - -{{< figure src="../copy-token.png" alt="Copy the token from LoRa Cloud" >}} - -Finish by clicking the **Set token** button. - -{{< figure src="../paste-token-modem.png" alt="Paste the token in The Things Stack" >}} - -## Obtain Location Solutions - -For LR1110 modem-based devices, location of the device can be estimated using Wi-Fi, assisted GNSS and autonomous GNSS scans. This section will show you how to obtain the location estimates using Wi-Fi and assisted GNSS scans. - -{{< note >}} Please keep in mind that this guide does not refer to LoRa Cloud Geolocation. In case you are looking for geolocation solutions that use RSSI and TOA metadata, or you are using LR1110-based device with transceiver firmware (instead of Modem-E firmware), you should follow the [LoRa Cloud Geolocation guide]({{< ref "/integrations/other-integrations/lora-cloud/geolocation-services" >}}). {{}} - -{{< note >}} The number of (useful) satellites detected when running the autonomous GNSS scan might not be enough to calculate the position of your device, so we will not include that case in this guide. However, if you want to read more about it, follow [this guide](https://lora-developers.semtech.com/learning-center/hands-on-labs/build-end-to-end-solution-using-lorawan-and-loraedge/find-the-location-of-your-tracking-device/#run-an-autonomous-gnss-scan-and-send-results). {{}} - -After you obtain the location results, you can further integrate your {{% tts %}} application with other third-party IoT platforms to visualize them, etc. - -### Wi-Fi Scans - -To learn how to perform Wi-Fi scans with LoRa Edge LR1110 device, follow [this guide](https://lora-developers.semtech.com/learning-center/hands-on-labs/build-end-to-end-solution-using-lorawan-and-loraedge/find-the-location-of-your-tracking-device/#run-a-wi-fi-scan-and-send-results). - -At this point, when your device performs a Wi-Fi scan and sends the resulting data in an uplink message, you will notice the location estimation results present in the `Location solved` message in {{% tts %}} **Live data** tab, as shown below. - -{{< figure src="../wifi-scan-result.png" alt="Location estimation result from a WiFi scan" >}} - -Notice the `Source: WIFI_RSSI_GEOLOCATION` which indicates the type of scan your device is performing. - -{{< warning >}} Keep in mind that the Wi-Fi triangulation is performed here, so you will be able to obtain location estimates only if your device's Wi-Fi scan resulted in 3 or more MAC addresses. If this is not the case, you will not see the `Location solved` message in {{% tts %}} **Live data** view, but you will not see any errors either. {{}} - -### Assisted GNSS Scans - -To learn how to perform GNSS assisted scans with LoRa Edge LR1110 device, follow [this guide](https://lora-developers.semtech.com/learning-center/hands-on-labs/build-end-to-end-solution-using-lorawan-and-loraedge/find-the-location-of-your-tracking-device/#configure-and-run-an-assisted-gnss-scan-and-send-results). - -{{< note >}} Keep in mind that in order to perform an assisted GNSS scan, you have to provide the approximate location coordinates to the LoRa Edge LR1110 device. {{}} - -Same as in the subsection above, when your device performs an assisted GNSS scan and sends the associated data in an uplink message, you will notice the location estimation results present in the `Location solved` message in {{% tts %}} **Live data** tab, as shown below. - -{{< figure src="../gnss-assisted-scan-result.png" alt="Location estimation result from an assisted GNSS scan" >}} - -Notice the `Source: GPS` which indicates the type of scan your device is performing. - -{{< warning >}} The device's active GNSS antenna should be placed outdoors in order to be able to detect as much satellites as possible. - -If you do not receive the `Location solved` message, it is possible that LoRa Cloud GNSS solver could not resolve your device's location. To verify, check the `log_messages` object in the `Service data` messages. You might see errors such as: - -- `Not enough received or usable satellites, totalReceived=4, usableGPS=3, usableBDS=0` if there is too few detected and/or usable satellites -- `Location fix dropped due to poor accuracy, caused most likely by big error in pseudo-ranges or timestamp` if the accuracy of the resulting location is too low - -If you are facing these errors, keep repeating the scan and re-sending results periodically until GNSS solver manages to resolve your device's location. Be aware that there is a high chance your device's battery will drain much faster if you are frequently repeating these steps. {{}} - -## Send Requests from LoRa Cloud - -Besides estimating the location of your device, you can also send requests from LoRa Cloud portal to mute or reset the device, trigger it for a re-join, set ADR profile or obtain information like temperature, voltage, signal strength, status, etc. In this section, we demonstrate how to send a request to obtain information from your device. - -To send a request, navigate to **Manage devices** on the left hand menu in the LoRa Cloud Modem Services portal. - -Click on the **Send requests** button. - -{{< figure src="../send-requests.png" alt="Send requests from LoRa Cloud portal" >}} - -Enter your device's EUI in the **EUI(S)** field and choose **Get Info** as a **Request type**. Tick the boxes next to the information you want to obtain from your device. - -Schedule the request to be sent by clicking the **Send requests** button. - -{{< figure src="../get-info.png" alt="Get Info request" >}} - -After a few moments, click on a reload button to refresh the device information in the **Manage devices** view. You can already see that the **Status** is changed to **Joined: Yes**, as well as the time of the **Last Uplink**, **Signal RSSI** and **Signal SNR**. - -Click the **>** button next to your device to see all the information that was obtained from the device. - -{{< figure src="../full-info.png" alt="Show full info" >}} diff --git a/doc/content/integrations/other-integrations/lora-cloud/paste-token-geolocation.png b/doc/content/integrations/other-integrations/lora-cloud/paste-token-geolocation.png deleted file mode 100644 index 402699a6fb..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/paste-token-geolocation.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/paste-token-modem.png b/doc/content/integrations/other-integrations/lora-cloud/paste-token-modem.png deleted file mode 100644 index e0a0183184..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/paste-token-modem.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/portal.md b/doc/content/integrations/other-integrations/lora-cloud/portal.md deleted file mode 100644 index d36020982a..0000000000 --- a/doc/content/integrations/other-integrations/lora-cloud/portal.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: "LoRa Cloud Setup" -description: "" -weight: 1 -aliases: [/integrations/lora-cloud/portal] ---- - -Before connecting your device to {{% tts %}} you need to set up the [LoRa Cloud portal](https://www.loracloud.com/portal) by creating an API token. - - - -## LoRa Cloud Portal Setup - -On the [LoRa Cloud portal](https://www.loracloud.com/portal), navigate to **Modem & Geolocation Services**. - -{{< figure src="../portal.png" alt="LoRa Cloud Modem & Geolocation Services" >}} - -Choose **Manage tokens** on the left hand menu. Click the **Create new token** button. - -Give the name to your token and tick the boxes next to permissions you wish to allow for it. Click the **Create new token** button to finish. A user can decide to restrict some permissions. On the image below, all permissions are allowed for the sake of simplicity of this guide. - -{{< figure src="../create-token.png" alt="Creating a token" >}} - -To add a new device, choose **Manage devices** on the left hand menu and click the **Add devices** button. You only need to provide the device EUI as shown on the image below. - -{{< figure src="../add-device.png" alt="Adding a new device" >}} diff --git a/doc/content/integrations/other-integrations/lora-cloud/portal.png b/doc/content/integrations/other-integrations/lora-cloud/portal.png deleted file mode 100644 index 816f581c0a..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/portal.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/send-requests.png b/doc/content/integrations/other-integrations/lora-cloud/send-requests.png deleted file mode 100644 index 87c7ac1da6..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/send-requests.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/toa-rssi.png b/doc/content/integrations/other-integrations/lora-cloud/toa-rssi.png deleted file mode 100644 index 7105b6bd7e..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/toa-rssi.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/toa-wifi.png b/doc/content/integrations/other-integrations/lora-cloud/toa-wifi.png deleted file mode 100644 index 9a0a68654f..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/toa-wifi.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/token-creation.png b/doc/content/integrations/other-integrations/lora-cloud/token-creation.png deleted file mode 100644 index ce1a5dd5b3..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/token-creation.png and /dev/null differ diff --git a/doc/content/integrations/other-integrations/lora-cloud/wifi-scan-result.png b/doc/content/integrations/other-integrations/lora-cloud/wifi-scan-result.png deleted file mode 100644 index 9eed5b7248..0000000000 Binary files a/doc/content/integrations/other-integrations/lora-cloud/wifi-scan-result.png and /dev/null differ