akenza.io
WebsiteAPI DocumentationWhat's newLogin
  • Overview
  • Getting Started
    • Connect a Device
  • Changelog
  • General
    • Applications
    • Organization context
    • Workspace Context
    • Users
      • User Roles
  • Device Management
    • Managing an organization
      • API keys
      • Users (Organization)
        • Add & removing users from your organization
    • Managing a workspace
      • General Settings
        • Device Lifecycle Reports
        • Workspace properties
        • Occupancy settings
        • Device Setup Assistant
      • Custom fields
      • Tags
      • Users (Workspace)
    • Devices
      • Device
      • Device Simulator
      • Bulk actions
      • Bulk import CSV templates
    • Rules
      • Input
      • Logic blocks
        • Comparison
        • Custom Logic
          • Logic Block Scripting
      • Timed Rules
      • Rule Actions
        • Downlink
    • Data Flows
      • Device Connectors
        • Device Security
          • Using Device Credentials
            • Creating Public/Private Key Pairs
            • Using JSON Web Tokens (JWTs)
              • Python
              • Java
        • HTTP
        • MQTT
        • CoAP
        • LoRaWAN
          • Connectivity Management
          • Swisscom LoRaWAN
          • The Things Network
          • Loriot
          • Actility’s ThingPark Wireless
          • EWZ
          • Cibicom
          • Helium
          • ChirpStack
        • NB-IoT
        • mioty
        • Disruptive Technologies
        • VergeSense
        • Spaceti
        • Haltian
      • Device Types
        • Custom Device Types
          • Uplink
          • Downlink
          • Scripting
        • Library
      • Output Connectors
        • Databases
          • akenza DB
          • InfluxDB
          • SQL Databases
        • Streaming
          • Webhook
          • Azure IoT Hub
          • AWS Kinesis
          • Google Cloud Pub/Sub
          • Apache Kafka
        • Notifications
          • E-Mail
          • SMS
          • Microsoft Teams
          • Slack
    • Custom Components
    • Integrations
    • Reference
      • REST API
        • Filtering
        • Querying Device Data
      • WebSocket API
      • Scripting
        • Stateful Operations
        • Utility Functions
      • Payload Templating
  • Reference
  • Dashboard Builder
    • Managing Dashboards
      • Embedding dashboards
    • Components
      • Map
      • Floorplan
  • Device Setup Assistant
    • Device Setup Assistant - Overview
  • Tutorials
    • BI Tools
      • Grafana Data Source Plugin
      • How to build a dashboard with Retool
      • How to analyze data with AWS QuickSight
    • Devices
      • How to integrate the XDK device from Legic via MQTT on akenza
      • How to connect the Disruptive Technologies-cloud on akenza
      • How to send Downlinks to the Kuando Busylight device
      • How to integrate an Arduino device via MQTT on akenza
      • Integrate a MClimate Vicki LoRaWAN Radiator Thermostat on akenza
      • How to integrate an ERS Elsys device with Loriot on akenza
      • How to integrate the IAM Decentlab device with TTN on akenza
      • How to integrate the Seeed SenseCAP T1000 tracker on akenza
      • How to integrate a Swisscom Multisense device on akenza
    • Notifications
      • How to send SMS notifications
      • How to send notifications to Slack
      • How to send notifications to Microsoft Teams
    • Enterprise solutions
      • How to send data to Azure IoT Hub
      • How to send data to the Google Cloud Pub/Sub
      • How to send data to InfluxDB
      • How to send data to AWS Kinesis
      • How to send data to Azure Event Hubs with Apache Kafka
    • IoT Starter Kits
      • How to integrate the IAQ Kit with Actility on akenza
      • How to integrate the CoWork Kit with Actility on akenza
      • How to integrate the Smart Building Kit with Actility on akenza
      • How to integrate the Pepperl+Fuchs Kit with Actility on akenza
  • Support Center
    • FAQ
    • Status Page
    • Service Desk
    • Request a feature
  • Deprecated
    • SIM-Cards
    • Everynet
    • Sigfox
    • How to connect the Yanzi Lifecycle cloud on akenza
Powered by GitBook
On this page
  • 1. Create a Data Flow
  • 2. Create the Multisense device
  • 3. Test your setup

Was this helpful?

  1. Tutorials
  2. Devices

How to integrate a Swisscom Multisense device on akenza

In this tutorial you will learn how to integrate the Multisense device on akenza

PreviousHow to integrate the Seeed SenseCAP T1000 tracker on akenzaNextNotifications

Last updated 1 year ago

Was this helpful?

Applications:

  • Workplace occupancy and doorways

  • Temperature & Humidity

  • General service button

Product features:

  • A simple plug-and-play solution with a range of different sensors in a compact, battery-powered device

  • Reduces the complexity of IoT projects and is quick to install without in-depth technical knowledge.

You will find more information about the Swisscom LoRaWAN Multisense device .

1. Create a Data Flow

Go to Data Flow in the left-side menu and select Create Data Flow. As we have a LoRa device, select LoRa as a device connector.

Use the search field to search for Multisense - General in the Device Type library. Proceed further to the Output Connector.

When the Service button gets pressed, an E-Mail shall be sent to a recipient. Sent data shall be also stored on the Akenza DB. Therefore select Akenza DB and E-Mail as output connectors.

Create the following Mail notification:

  • Name: Service on Demand

  • Subject: Service request

  • Message: You have a Service request.

  • Recipients: Your mail address

Once your mail notification is created, proceed with Save Data Flow. Now you are ready to create the Multisense device in the Asset Inventory.

2. Create the Multisense device

To create a new device, select Create Device in the Asset Inventory.

Add a device name and choose the Data Flow of the Multisense that you just have created.

Fill in the Connectivity Parameters about your Multisense device and select Create Device.

Once created, you will see now your Multisense device in the Asset Inventory Overview.

Connect now the Multisense device to join the network by pressing the Multisense button for three seconds. The green LED will flash accordingly. The device starts to join the network, which is indicated by a short blink sequence in green. If the join was successful, the sequence will be followed by a long green blink. If the join failed, this will be indicated with a red blink. With a button press of 3s or longer, a restart of the device can be initiated at any time.

Once the device has joined the network, the Connectivity Status on the Asset Inventory of your device will be displayed with a green icon.

2.1 Configure your device mode per downlink

Now with your device up and running, you can configure different device modes with a downlink. In this tutorial, we use the Downlink HEX string of the Multisense button mode.

Device modes

Downlink Hex string

Service Button

[PINCODE]b8a710030000000080817f7f000000000000

Temperature & Humidity

[PINCODE]0827100300001e0130007f7f000000000000

Workplace occupancy

[PINCODE]082710030100050607

Reed (door) counter

[PINCODE]0827100300003c0140a17f7f000000000000

Vibration

[PINCODE]0827100300003c0108007f7f0000000a2000

General (all sensors on)

[PINCODE]0880640300000001f8e17f7f0000000ae555

[PINCODE] = first 4 characters and last 4 characters of your Application key Port = 100

Swisscom Multisense Service Button

This mode will trigger a network-confirmed uplink message for each button press. If the button isn't pressed within 24 hours, the device will trigger a life sign message to report it is still working and under network coverage.

Swisscom Multisense Temperature & Humidity

This mode reports the temperature and relative humidity of the sensor in regular intervals.

Swisscom Multisense Workplace occupancy

This mode will use the internal accelerometer to measure the occupation of a desk by the vibrations on that surface. The occupancy or usage of any other object could also be measured, however, the configuration of this mode is matched for the workplace occupancy.

Swisscom Multisense Reed (door) counter

This mode reports how often a magnet has approached the reed contact on the device sufficiently. With an appropriate installation on the door, this mode can be used eg. to count the number of times a door is opened. Use cases: Door counting, predictive maintenance, monitoring of moving parts etc.

Swisscom Multisense Vibration

This mode counts the number of times acceleration is detected above the defined threshold, no matter the directionality.

Swisscom Multisense General (all sensors on)

This mode is only for demo purposes and enables all sensors for immediate feedback on the device while demonstrating. The demo mode is not intended for productive use and might drain the battery quickly. After using the demo mode, please reset the device to a standard mode.

To send the downlink to your Multisense button device, go to Downlink on the Asset Detail View. Insert the Downlink HEX string as well Port 100 and press Send message. You will get notified if the Downlink was sent successfully.

3. Test your setup

Go to Message Logs on the Device Detail View of your Multisense device to see incoming data. Press the Service button and check if you receive the Service-Request via E-Mail.

Congratulations, you have successfully integrated your Multisense button device.

Make use of the akenza offer. Therefore you do not need to have an account ready from a network provider. You simply connect your LoRa device to a network provider which is hosted and managed from akenza. Select Swisscom LPN and proceed to the Device Type.

here
Multisense of Swisscom
Device connector
CaaS device connector
Device type Multisense - General
Output connector Akenza DB & E-Mail
Create new device form
Connectivity parameters
Connectivity Status on Asset Inventory Overview
Downlink settings
Connectivity-as-a-Service