Skip to main content

Other integrations

Yggio integrates with more systems than have a page of their own. This one collects the rest: what each brings in or sends out, and where it is set up. None of them need a page to themselves, but knowing they exist saves rebuilding something that is already there.

They fall into two groups by direction, which is the first thing to establish about any integration, since few of them go both ways. Delta Controls and Siemens Desigo CC appear in both lists, and that is not the same integration counted twice: reading from a system and writing back to it are set up separately, and having one does not give you the other.

Coming in​

These create devices in Yggio from someone else's system or service. Most are older than the connector picker and are created from New Device in the device list rather than under Connectors.

IntegrationWhat it brings inCreated from
CelsiviewSensor data from the Celsiview portal, typically NB-IoT devicesNew Device
Klimator RSIRoad weather data from Klimator's road weather stations, through their RSI portalNew Device
Delta ControlsA building management system, through the EnteliWeb REST APINew Device
Siemens Desigo CCA building management systemNew Device
The Things NetworkThe TTN LoRaWAN network serverNew Device
BLE DusoniotBLE gateways from DusoniotNew Device
Open Weather MapWeather and forecast for a latitude and longitude, as a weather deviceNew Device
Elvaco CMeMeter readings over HTTP from an M-Bus gateway, report template 3108The gateway's own config
BACnet IPEquipment on a BACnet network, reached directlyContact support
Modbus TCPEquipment on a Modbus network, reached directlyContact support

The last two need direct network access, which is why support enables them rather than the picker. For BACnet and Modbus, see Building automation, which covers the four ways into a building and when reaching the equipment directly is the right one.

Elvaco CMe​

An Elvaco CMe gateway reads the meters on its M-Bus and posts them to Yggio on a schedule. Nothing is configured on the Yggio side beyond a user account: the gateway holds the whole configuration and Yggio never polls it.

This integration predates the connector pattern and does not follow it. There is no connector to create and no translator to assign, the gateway signs in with a Yggio user's username and password rather than with a credential set, and the payload is CSV rather than JSON. That is how it works today, so follow the steps below rather than the pattern used elsewhere in this section.

Setting it up

  1. Create a Yggio user for this integration and nothing else. The gateway signs in as that user, and every device it creates is owned by that user. A dedicated account keeps the meters out of a person's own estate and lets the credentials be revoked on their own.
  2. In the CMe's report configuration, set the URL to https://<your Yggio>/http-push/elvaco, the username and password to that Yggio user's, and the report template to 3108.
  3. Set the reporting interval on the gateway. Whatever it sends, Yggio accepts.

What arrives

Template 3108 produces a semicolon-separated CSV whose header row begins #serial-number. Yggio parses it and creates or updates one device per meter, so a gateway reporting sixty meters produces sixty Yggio devices rather than one device with sixty fields.

  • Rows are matched to a device on device-identification. That is what makes the second report update the first report's device instead of creating another.
  • A device created this way is named Elvaco-<device-identification>.
  • Every column in the report becomes a field on the device, so whatever the template carries - volume, energy, flow, temperature - arrives named and usable in views, rules and reports.
  • created becomes the reading's timestamp. reportedAt is when Yggio received the report.
  • Decimal commas are converted, so 12,345 arrives as the number 12.345.

Rows missing either #serial-number or device-identification are discarded and logged. If meters are missing in Yggio, that is the first thing to check.

If a report does not arrive

ResponseMeaning
200Accepted
401The username or password is wrong
400The upload could not be read as the expected CSV, usually the wrong report template
500Authenticated and parsed, but saving the devices failed

Going out​

These are channels, not connectors. A channel is created on a device and publishes that device's data to an external system as it updates.

A channel usually needs a connector behind it, and over time all of them will. Treat a connector as part of setting up a channel rather than as an alternative to it.

ChannelWrites to
Azure IoT HubAn Azure IoT Hub, using a connection string
Siemens Desigo CCSiemens Desigo CC
Delta ControlsDelta Controls
VyerVyer
HTTPAny URL you provide, which is the webhook case
MQTTYggio's own broker

Some of the named ones need field mapping, since the receiving system has its own field names. Channels are created per device under Channels, or across many devices at once with Select many.

If what you need is not here​

This page is not the complete list, and it is not meant to be. Yggio carries a number of customer-specific integrations that are not documented publicly, because they were built for one organisation's systems and would mean nothing to anyone else. Connectors also exist that are not in the picker, and more are added over time.

So the absence of a system from this page says nothing about whether Yggio can integrate with it. Ask your support representative before assuming an integration has to be built from scratch.