Develco Squid.link 2X Specification sheet

GetStartedGuide.md 6/3/2021
1 / 12
Connect Smoke Safety Basic Kit to your Azure IoT
services
Table of Contents
Introduction
Prerequisites
Prepare the Device
Connect to Azure IoT Central
Integration with Azure IoT Explorer
Additional links
Introduction
About this document
This document describes how to connect the Smoke Safety Basic Kit to Azure IoT Hub using the Azure IoT
Explorer with certified device application and device models.
IoT Plug and Play certified device simplifies the process of building devices without custom device code. Using
Solution builders can integrated quickly using the certified IoT Plug and Play enabled device based on Azure
IoT Central as well as third-party solutions.
This getting started guide provides step by step instruction on getting the device provisioned to Azure IoT
Hub using Device Provisioning Service (DPS) and using Azure IoT Explorer to interact with device's capabilities.
Prerequisites
You should have the following items ready before beginning the process:
For Azure IoT Central
Azure Account
Azure IoT Central application
For Azure IoT Hub
Azure IoT Hub Instance
Azure IoT Hub Device Provisioning Service
Azure IoT Public Model Repository
Prepare the Device.
Development Environmental setup

GetStartedGuide.md 6/3/2021
2 / 12
IoT Plug and Play Certification is certifying specific device code implementation against specific device model.
Device builders should either pre-install device code or make the binary download-able.
Capabilities of the device
The Squid.link 2X Gateway has options for ZigBee, Z-Wave, Wireless M-Bus, Bluetooth Low Energy (BLE), and
WLAN HAN networks. Communication with servers and e.g. smartphones can be established via WLAN,
Ethernet (to local modem) or cellular networks. The price is extremely competitive since you will only pay for
your selected communication modules.
The gateway includes processor power to implement even very complex local intelligence. The memory
options leave room for data storage and logging. You are no longer dependent on one vendor but can
combine your Home Area network exactly the way you prefer.
The code is pre-installed on the device. In the following steps you will find instructions on how to configure
your device.
How to setup the device and connect it to the Internet
Ways to get started – Find below two ways to connect to the Squid.link gateway and accessing the web
interface;
1. Via ethernet
2. Via WLAN
Via ethernet
Connect the gateway to your local network using an ethernet cable and apply power to the gateway. The
gateway is configured to use DHCP, so make sure a DHCP server is available on the network. Note: The
gateway should not be connected directly to the PC.
Open a browser and apply one of the following options:

GetStartedGuide.md 6/3/2021
3 / 12
1. Enter the IP address of the gateway.
2. Enter ”gw-xxxx.local” in a browser where xxxx is the last 4 characters of the gateway serial number
(preceding zero must be removed, e.g. 0366 => ”gw-366.local”) The gateway serial number is included
on the product label of the gateway as shown below. If issues occur, you can download and install
”Bonjour Print Services” on your PC as an alternative.
Via WLAN
Apply power to the Squid.link gateway. Once the gateway has booted, it will start an access point named
”squid.link-xxxx” where xxxx is the serial number of the gateway.
Connect your PC to the access point through your PC’s network and Wi-Fi manager and access it like any
other wireless network.

GetStartedGuide.md 6/3/2021
4 / 12
Enter the last 8 characters of the installation code as the password. The installation code is included on the
product label of the gateway.
Note: Do not include any blank spaces and do not use capital letters for the password.
After connecting to the access point, open an internet browser, and enter the IP 192.168.2.10 into the address
bar. This will direct you to the web interface.
Note: The gateway access point does not provide internet access. To browse the internet, you will need to
connect to a different wireless network or use an ethernet port.
Adding devices
Click on + in the bottom right corner to add devices. A dialog box opens and shows the available devices. You
can add devices in two ways:
1. Automatically: Select a device from the list, and click ”Add”
2. Manually: Type in the serial number and installation code of the device.
Click on the ”Devices” tab to get an overview of the added devices as well as the default parameters and
essential data points. These include the temperature, consumed energy, or if an alarm has been triggered.

GetStartedGuide.md 6/3/2021
5 / 12
The API doc is also available directly on the gateway or Internet. It can be accessed at the following URLs:
http://{hostname}/api-docs/interactive/index.html#/
http://api.squid.link/
The interactive documentation will allow you to try out the API calls directly from the browser.
The API can be accessed over HTTP or by connecting to a WebSocket or a raw socket. When using HTTP the
message pattern is request/response. The WebSocket and raw socket wrap the REST API and adds support for
push messages. Messages are pushed when a resource is: added, removed or updated.
The raw socket can be access on port 10000 and only from localhost. The WebSocket and HTTP interface is
available on port 80. The port number can be changed in the configuration file.

GetStartedGuide.md 6/3/2021
6 / 12
Configuring Squidsmartapp Azure IoT Handler
This section demonstrates how to configure the Azure IoT Handler by using the required parameters, to
connect to an Azure IoT Hub, through an Azure Device Provisioning Service.
First step is to go to /config/azureiot of the Squidsmart api and press Try it out and paste config information
and then execute buttons. The api command requires the following parameters, when using Symmetric Key as
security:
• mode: Security mode: SymmetricKey.
• deviceKey: Primary key from key pair.
• registrationId: Registration id for the gateway, if gateway EUI’s are used on the cloud side, this parameter
can be set to “${production.gateway.eui}”.
• globalEndpoint: Global device endpoint associated with targeted Azure Device Provisioning Service.
• scopeId: ID scope associated with targeted Azure Device Provisioning Service.
• modelId: ID of targeted DTDL template to match.
Aditionally the gateway requires a complete model mapping, containing a full list of end-devlce EUI’s as well
as the DTDL model tags to map to.
If connection is successful, you can see the following message at /config/azureiot/status, telling the handler is
started and connected.
Connect to Azure IoT Central

GetStartedGuide.md 6/3/2021
7 / 12
This section describe how to connect to Azure IoT Central.
1. Create your app.
2. Insert the application name and choose your pricing plan.
3. To configure a device to connect to Azure IoT Central you need the following
ID scope: In your IoT Central application, navigate to Administration > Device Connection. Make a note
of the ID scope value.
Group primary key: In your IoT Central application, navigate to Administration > Device Connection >
SAS-IoT-Devices. Make a note of the shared access signature Primary key value.
Use the Cloud Shell to generate a device specific key from the group SAS key you just retrieved using the
Azure CLI

GetStartedGuide.md 6/3/2021
8 / 12
az extension add --name azure-iot
az iot central device compute-device-key --device-id sample-device-01 --pk
Make a note of the generated device key, and the ID scope for this application and flash it on the device
4. Another way in which you can retrieve the key is by creating a device (please note that you can use the
Gateway Serial Number as the deviceId).

GetStartedGuide.md 6/3/2021
9 / 12
5. After creating the device, you can find the Scope ID, the Device ID and the primary key in the "Connect"
section at the top right.
6. After making the PUT call with this information, you will be able to see the raw data within the page
after a few minutes via the API (please note that the deviceKey in the PUT request is the while the
registrationId is the deviceId yuo provided).
Integration with Azure IoT Explorer
Open your Device Provisioning Services, go to Tab "Manage Enrollments" and then "Add individual
enrollment".

GetStartedGuide.md 6/3/2021
10 / 12
Mechanism: Symmetric Key
Registration ID: ${gateway serial number}
IoT Hub Device ID: gw-${gateway serial number}
Now please follow the same steps as connecting to the Azure IoT Central noting that the registrationId will be
the serial number of the gateway and the deviceKey will be the individual enrollment primary key (open the
individual enrollment to be able to copy it).
In order to connect your Gateway to the IoTHub Explorer, you have to retrieve the Connection string. To do
so, go to your IotHub, Tab "Shared access policies" and then click "iothubowner". From the window that will
pop up, copy the "Primary connection string".

GetStartedGuide.md 6/3/2021
11 / 12
Opening the Explorer, in the HomePage, clicking on the tab "IoT Plug and Play settings", you will be able to
configure the repository containing the public model. Click on "Add", select "Public Repository" and then save.
Next, clicking on the tab "IoT Hubs" you will be able to add a connection. Just paste into the window that will
pop up the Connection string you retrieved from the Hub.
You will find your IoTHub in the HomePage. Just click on it to access it.
Accessing it, you will be able to see your device. Click on it.

GetStartedGuide.md 6/3/2021
12 / 12
Below you can see the interface that allow you to retrieve the data regarding the Device Identity.
Below you can see the preview of the Digital Twin.
Clicking on the tab "Direct method" you will be able to send commands to your device.
Clicking on the tab "Telemetry" you will be able to check the teletry sent from your device.
Clicking on the tab "IoT Plug and Play components" you will be able to check the Plug and Play model
retrieved from the public repository.
Additional Links
Import the Plug and Play model
Configure to connect to IoT Hub
Squid.link 2X Technical Specifications