reubenmiller

1. restart state file is not being deleted (after image has been restarted)

After a successfully completed firmware workflow, if the tedge-agent service is restarted, then tedge-agent will reprocess the restart-current-operation file again as the file is not deleted after the workflow has been completed.

file: /data/tedge/.agent/restart-current-operation

// cat /data/tedge/.agent/restart-current-operation
{"target":"device/main//","cmd_id":"c8y-mapper-2023-11-26T12:26:39.248420821Z","payload":{"status":"executing","context":{"command":{"topic":{"name":"te/device/main///cmd/firmware_update/c8y-mapper-2023-11-26T12:26:39.248420821Z"},"status":"rollback_restart","payload":{"name":"core-image-tedge-mender-raspberrypi4-64","reason":"Nothing to commit. Either the boot loader triggered the rollback, the device was rebooted after switching to new partition, or someone did a manual rollback!","remoteUrl":"https://t2873877.latest.stage.c8y.io/inventory/binaries/4785008","status":"rollback_restart","

reubenmiller

Onboarding thin-edge.io to Cumulocity IoT without auto registration enabled

Part 1: Create and upload the device certificate without auto registration

1. On the device, create the device certificate

   tedge cert create --device-id mytestdevice001

reubenmiller

Copy managed objects across tenants

Long Version

1. Activate a session to the source tenant

   set-session
   

reubenmiller

Before creating a custom operation handler, create the configuration and confirm that the operation will be delivered to the device. Once you have confirm this, then you can add your custom handler.

Part 1: Send operations from Cumulocity IoT to thin-edge.io

Below shows the steps to create a custom SmartREST collection for Cumulocity IoT, and how to check that the message arrives on the local thin-edge.io MQTT broker.

1. Create a SmartREST template collection in Cumulocity IoT, and create a custom "response"

   Below is an example collection which create two custom operations for the message ids:

reubenmiller

#!/bin/bash
########################################################################################################################
# Debug script to check the behaviour of the tedge-mapper-c8y/mosquitto and the responsiveness of the
# Cumulocity IoT token request/response topics (c8y/s/uat and c8y/s/dat).
#
# The script does the following:
# 1. Install a systemd service (and enables it)
# 2. Create mqtt subscriber to c8y/s/dat
# 3. Publish a mqtt message to c8y/s/uat
# 4. Wait for a message on the c8y/s/dat topic (give up after a few seconds)

reubenmiller

Using custom topic schema with thin-edge.io (>= 0.13.0)

This is a short informal overview of how to use thin-edge.io and a custom topic schema to model different IoT use-cases.

This documentation is provided to help people understand thin-edge.io and to provide some early feedback before adding it to the official docs.

Building management system

This example explores the building management system use-case where thin-edge.io provides the communication from the cloud to a local piece of software which translates the thin-edge.io MQTT API to the required building management system API calls.

reubenmiller

"""thin-edge.io data simulator"""
import argparse
import time
import random
import json
from multiprocessing import Pool
import datetime
import logging
import paho.mqtt.client as mqtt

reubenmiller

#!/bin/sh
MODEL=$(cat /proc/cpuinfo | grep Model | cut -d: -f2- | xargs)
OS_NAME=$(cat /etc/os-release | grep PRETTY_NAME | cut -d= -f2- | tr -d '"')

printf '\n'
printf 'Debug information: (copy/paste to the ticket)\n'
printf '\n'
printf '|Property|Value|\n'
printf '|--------|-----|\n'
printf '|OS [incl. version]|`%s`|\n' "${OS_NAME:-unknown}"

reubenmiller

Manually download and install the binary

1. Download the binary

   Linux / MacOS / WSL

   Make sure you choose the appropriate cpu architecture for your machine! Check out the options in the assets section of the latest release.

   mkdir -p "$HOME/bin"

reubenmiller

#!/bin/sh
# -----------------------------------------------------------------------------------------------
# thin-edge.io debugging
# -----------------------------------------------------------------------------------------------
# Collect debug information to access the health of the installation
# -----------------------------------------------------------------------------------------------
set -e

LOG_FILE=/tmp/tedge-debug.log