Integration overview

Pressac partners with UMA to create intelligent workplaces

Enabling organisations to monitor real-time workspace occupancy and environmental conditions, improving user experiences and helping reduce operational costs and carbon footprint.

Smart-building sensor manufacturer Pressac Communication has entered a partnership with workplace intelligence software provider UMA, to provide integrated technology which transforms workplaces into super-intelligent, highly responsive spaces.

The combination of Pressac’s smart sensors with UMA’s leading-edge software allows businesses to monitor real-time workspace utilisation and capture environmental insights to create a more efficient, safer and sustainable working environment.

Pressac’s smart sensors use advanced wireless technology, which allows them to be kept separate from an organisation’s IT network. This makes them easy to install and integrate real-time data straight into UMA’s software. Their ultra-low power consumption means they need minimal maintenance, with batteries typically lasting over five years.

Getting started

To understand more about Pressac's IoT sensors click here.

UMA supports the following Pressac sensors out of the box:

Desk occupancy sensor

Room occupancy sensor

Co2, temperature and humidity sensor

Current monitoring sensor

Pulse counter

Firewall rules

To check relevant Pressac firewall rules click here.

Out of the box, UMA supports four manufacturers of IoT sensors.

However we can support custom IoT integrations if you email support@askuma.ai to find out more.

Please choose from the below options to understand the types of sensors we integrate with.

LoRaWAN sensors

Configuration guides

To configure Milesight LoRa devices it's recommended to install the Milesight Toolbox application on your mobile device. This connects to Milesight devices via NFC using your phone.

The Toolbox application is useful for configuring sensor payload settings. From here you can speed up or slow down messages reporting to UMA.

To add a Milesight LoRa sensor to a Milesight gateway, follow the instructions in this guide:

To connect the Milesight gateway to UMA's MQTT server follow the instructions in this guide:

Payload codec

In order for our server to correctly understand messages sent from LoRa sensors and devices you will need to create a custom payload codec on the Milesight gateway for each device type.

Once created you will need to add the following text at the end of the payload:

decoded.devEUI = LoRaObject.devEUI;

decoded.rssi = LoRaObject.rxInfo[0].rssi;

decoded.snr = LoRaObject.rxInfo[0].loRaSNR;

decoded.data = LoRaObject.data;

decoded.time = new Date().toISOString();

This text should be inserted before the return decoded statement.

For more information please check out Milesight's documentation here.

Application setup

In order for our server to correctly understand uplinks and downlinks from our server you will need to configure the application on the gateway with the following details:

Uplink - milesight

Downlink - milesight/downlink/$deveui

Add the device to UMA

To add a Milesight LoRa sensor to UMA, you will need the Dev EUI which can be obtained either locally on the sensor or by using the Toolbox application or Milesight gateway. Use the Dev EUI as the UMA ID.

When adding a Milesight device in UMA, click on add device and then use the Milesight card to find the device you want to add.

After some minutes, the device will come online and you will start recording the data coming from the sensor.

For information on configuring the Milesight DS3604 follow the guide here.

PoE sensors

Configuration guides

To configure Milesight people counting sensors use the following guides:

Milesight VS121 - https://resource.milesight-iot.com/milesight/document/vs121-p-user-guide-en.pdf

Milesight VS133 - https://resource.milesight.com/milesight/iot/document/vs133-user-guide-en.pdf

Use the guides above to connect the sensor to UMA's MQTT server.

Add the device to UMA

To add a Milesight PoE sensor to UMA, you will need the serial number which can be obtained either locally on the sensor or from the device web GUI. Use the serial number as the device ID.

When adding a Milesight device in UMA, click on add device and then use the Milesight card to find the device you want to add.

After some minutes, the device will come online and you will start recording the data coming from the sensor.

Integration overview

We're thrilled to show you an exciting integration with our esteemed sensor partner, Milesight.

This collaboration represents a significant advancement in our IoT capabilities, as we join forces with one of the foremost manufacturers in the global IoT industry.

With this integration, you have the opportunity to seamlessly integrate Milesight sensors into the UMA platform, allowing for comprehensive insights into both occupancy patterns and the environmental conditions within your building.

To find out more about Milesight’s IoT range click here.

Getting started

We support two types of Milesight sensors - LoRaWAN and network based PoE sensors.

UMA is able to ingest sensor data from any Milesight IoT device provided that your device, gateway or network server is sending the sensor payloads to UMA's MQTT server.

LoRaWAN sensors

LoRaWAN sensors are employed in cases where real-time information isn't crucial, and a data synchronisation every 20 minutes (as an example) suffices. These types of sensors are as follows:

• Desk sensors

• Environmental sensors

• Energy sensors

If you have purchased or are planning on purchasing a Milesight LoRaWAN sensor, you will need a gateway to establish a connection from the sensor to our servers.

We recommend the following gateways as they have built in LoRa network servers:

Milesight UG65

Milesight UG63

If you already have access to your own LoRaWAN network server, you just need create a connection to UMA's MQTT server.

PoE sensors

Network based PoE sensors are used where real-time information is crucial such as a people counting sensor.

We support the following Milesight PoE people counting sensors:

Milesight VS121

Milesight VS133

Firewall rules

To check relevant Milesight firewall rules click here.

LoRaWAN explained

• End Devices - sensors or actuators send LoRa modulated wireless messages to the gateways or receive messages wirelessly back from the gateways.

• Gateways - receive messages from end devices and forward them to the Network Server (if the network server is not built into the gateway)

• Network Server - a piece of software running on a server that manages the entire network. This can be built into a gateway.

• Application servers - this is UMA.

For more information, visit here.

Integration overview

UMA's advanced intelligent meeting room software, seamlessly fused with state-of-the-art Irisys occupancy sensor technology, offers a cutting-edge solution that revolutionises the way businesses interact with their workspace environment.

The Irisys occupancy sensors, equipped with highly sensitive and precision-driven detection capabilities, provide granular insights into real-time occupancy patterns within meeting spaces. These sensors utilize advanced algorithms to detect and analyze the presence and movement of individuals, offering a nuanced understanding of how these spaces are utilized over time.

UMA's software acts as the central hub, intelligently processing the data gleaned from the Irisys sensors. This powerful platform employs sophisticated algorithms and machine learning techniques to transform raw occupancy data into actionable insights. These insights encompass a wide array of metrics, including peak utilization times, average meeting durations, and patterns of room occupancy. Moreover, UMA's software can be customied to generate detailed reports and visualizations, allowing facility managers and decision-makers to make data-driven decisions for optimizing their building's layout and resources.

Getting started

UMA integrates with the Irisys Vector 4D people counting sensor.

UMA ingests Irisys' people count data by configuring the sensor to send data to UMA's MQTT server.

Firewall rules

To check relevant Irisys firewall rules click here.

Installation Best Practices

The sensor manufacturer (Irisys, a FLUKE brand) provides a detailed PDF including the recommended mounting height range, it is recommended to be reviewed before proceeding with the next steps. The link to the article can be found here.

Network Security

This section discusses the network and security features available on the Irisys Vector devices. This information can be used for infrastructure planning and network routing and provides peace of mind that your Vector device is a modern, secure, IoT (internet of things) platform, designed for use on modern, high-speed, retail and commercial networks.

Internal Ports (Used for initial configuration of the sensor & management)

The device also supports DNS, DHCP and ICMP (ping) and thus these should be enabled/open as well.

Outbound Traffic

Encryption Process

For data in transit, the Vector 4D uses TLS 1.2 encryption as standard; this is invoked automatically for web traffic over HTTPS and is used for proprietary data communication with Irisys tools (e.g. Estate Manager). A self-signed certificate is used by default, but the ability to replace this with an uploaded 3rd party cert is provided – this is recommended if using HTTPS for web/Rest API.

GDPR & PCI Compliance

Vector 4D devices utilise Time of Flight technology, which illuminates the area below the device with invisible infrared light. The reflected signal is detected, and the time taken to return is used to build up a height map of the scene which is then used to track people through the field of view. This technology does not have any associated GDPR issues.

A CCTV component is included to allow for initial configuration (via a remote workstation if required), and for any validation audits to be performed, for example, if the accuracy is ever questioned.

The CCTV image is only used for these two purposes, and the resolution and image quality provided from the onboard CCTV component is purposefully as low as possible in order to reduce bandwidth requirements and also negate any PCI compliance issues. Because the CCTV image is not used internally by the device for any of the tracking or counting functionality, the CCTV lens can be permanently covered if privacy is of concern (once configured).

Stored Images

Because a Vector does not use CCTV images for any of its counting functionality, images are not processed or stored during normal operation. When configuring the device remotely, video is streamed to allow the setup process, but these frames are not stored and are simply thrown away. Only when recordings are captured for validation purposes does the storage of images become relevant. It should be noted that recordings used for validation purposes are only used when absolutely required – usually to fulfil contractual obligations – and the video only captures images of people’s heads, in low-quality, low-resolution images, and usually from some distance away. Once accuracy has been established the recordings should be deleted by the one validating. If validation is done through the Estate Manager platform, recordings are deleted automatically on a rolling schedule.

Configuring network settings on the Irisys sensor

It may be advisable to assemble your own isolated network consisting of a PoE switch and connection cables so that a connection can be made and the main settings changed before adding to your production network.

A new, previously un-configured, Vector Analytic or Vector Count device comes from the factory with a default IP address of 192.168.0.10.

It is recommended on the machine used to configure these devices the IP address is set to a value close to the default IP address for example 192.168.0.11 - This will allow you the ability to browse directly to the Vector Sensor if on an isolated network.

Performing the above is not recommended on a production network as you may cause IP conflicts or be unable to route to that specific subnet, it is recommended you change the IP details with the values provided by your IT department.

The Vector is password-protected to prevent malicious changes via a web browser connection. This can be changed during configuration if required.

The default username and password required for web access are:

Username: admin Password: installer

You will be prompted to change this after a successful first-time login

Once you are connected to your Vector, the network settings are accessed via the ‘Settings’ tab, then ‘Network’:

IP Settings

The Hostname is an alternative way of addressing a Vector rather than using the IP address. This functionality is network-dependent and may not work in some locations.

To use a DHCP assigned IP address, tick the ‘Enable DHCP’ checkbox. Again, the network administrator will need to specify whether to use a DHCP or a static IP address.

DNS Settings

The DNS (Domain Name System) settings are used by the Vector to resolve the IP addresses of any hostnames used. If the settings are incorrect, or they relate to an unreachable server address, the IP address resolving process will not succeed and the Vector will not be able to make a connection to a hostname. DNS settings are therefore required when connecting to a hostname for MQTT, HTTP Post, or an Outbound Connection.

If there are any preferred DNS servers on the same network as the Vector, enter their IP address(es) here. Up to three DNS server IP addresses can be entered if required.

By default, the freely available Google DNS server details will be present: 8.8.8.8 and 8.8.4.4. These can be changed if required or a third DNS server IP can simply be added. Note that the Google DNS servers may not be reachable on some networks, and in these cases, alternative DNS server settings will need to be made.

Configuring MQTT Settings & UMA Estate Manager Management

The steps listed below will onboard the sensors to the UMA Estate Manager, this will allow for remote management of each sensor & the ability for UMA Vision to take live & historic Occupancy data and display this within UMA Vision & outside meeting spaces using our 10" LED Panels.

UMA Estate Manager Connection Settings

1, Login to the sensor and navigate to "Settings" - "Site"

• Device Name: Provide a Device Name

• Site ID: (Please Obtain this Site ID from UMA, this is used to connect your Vector to Estate Manager & is important it is correct)

• Site Name: Provide a Site Name

2, Navigate to "Settings" - "Outbound Connections"

Enable Client 1 & enter the following details

• Address: http://uma.irisyscloud.net

• Port: 5000

• Reconnection Interval: 60

Select Test Connection & then save the settings applied.

If you see the sensor added when logging into https://uma.irisyscloud.net you have successfully added the device. If you are adding multiple devices you will need to perform the same steps.

MQTT Configuration Settings

We now need to configure the Vector with two MQTT Servers, to do this follow the below steps

1, Navigate to "Settings" - "MQTT" (If you are doing this from the Estate Manager you will need to toggle on Live View to make these changes which is located at the top of the page)

2, Select Add under MQTT & enter the following details

• Address: humble-newsreader.cloudmqtt.com

• Port: 8883

• Keep Alive (Seconds): 60

• Max History (Hours): 24

• Toggle on Credentials & enter the credentials provided to you by UMA

• TLS: Enabled

• Register Filter: Disabled

• Topic Counts: Enabled

• Status: Enabled

• Targets: Disabled

• Live Counts: Enabled

When toggling on these switches the fields underneath each toggle should self-populate data, please do not change the values.

You should now select, "Test Connection" - If you have any issues please speak with our support team by contacting support@askuma.ai

Configuring Occupancy Settings & Adding sensors to UMA Vision

On each sensor you must configure the following:

• Calibrate the sensor after installation

• Add IN & OUT lines

• Add an Occupancy Register

• Move the lines to where you need them to be

• Add the sensor to UMA Vision

To get started use the Milesight Toolbox application to turn on the device.

For more information on initial configuration, follow Milesight's guide here.

Once your device is on, you will need to upload a custom template to allow the device to work with our platform.

The custom template can be found here.

Ensure that the template has been added to Template 1.

From there, you are able to customise this template if you wish, as long as the module ID of the resource name and QR code stay as follows:

• Resource Name - Module 1

• QR Code - Module 3

Finally, follow the initial guide here to add your Milesight DS3604 LoRaWAN device to UMA.

Once you have added this device to a resource, the device will automatically update its resource name and QR code and you can use the check in application.

To visualise data from IoT sensors in UMA you will need to connect your device or IoT gateway to UMA's MQTT server.

Different IoT vendors and technologies have different ways of utilising MQTT, whether through an IoT gateway or network server.

If you configure your IoT gateway or network server to connect with UMA's MQTT server, the data will transmit smoothly, assuming the sensor is compatible.

For more details on UMA's MQTT server email us at support@askuma.ai.

MQTT explained

For more information on MQTT take a look at AWS' guide here:

Gateway setup

This guide assumes you’ve already connected your gateway to either an Ethernet, Wi-Fi or LTE network.

If you haven't, follow the manufacturers set up guide below:

Log in to the gateway via a web interface and navigate to connections and MQTT and enter in the following details:

• Default Client ID: {gateway name}

• Root Topic: umavision

• Device Identifier: Device ID

• Included Data: Tick All

• MQTT Connection Name: UMA Vision

• Client ID: Use Default

Add a device to UMA

To add a Pressac IoT sensor to UMA, you will need the Device ID which can be obtained either locally on the sensor or from the Pressac gateway. Use the Device ID as the UMA ID.

When adding a Pressac device in UMA, click on add device and then use the UMA card to find the device you want to add.

After some minutes, the device will come online and you will start recording the data coming from the sensor.

Repeater setup

Repeaters are used to boost the signal to allow sensors to connect to the gateway without adding an additional gateway.

Follow the manufacturers set up guide here:

Sensor installation guides

Desk occupancy sensor

Room occupancy sensor

Co2, temperature and humidity sensor

Current monitoring sensor (3 channel)

Current monitoring sensor (1 channel)

Pulse counter