With next release, we will clean up the message structure that also impacts the messages being forwarded to your servers. Currently, the array of keys includes:

1. key
2. value
3. unit (in some cases, e.g. °C for key temperature  or % for key humidity)
4. isCode (flag telling if the key should be translated using list of values or not
5. _id of the key item

The key’s attributes: unit, isCode, and _id were there historically since version v1 and are not needed anymore, so we want to remove them from the message to make the messages smaller and be more efficient. It does not make sense to send a unit of temperature with every temperature since it does not change and we keep it as a part of our config files. Same with isCode. These attributes were mainly used internally. 

The new message will keep this structure: 

{
  keys: [
    { key: 'action', value: 'gas_periodic' },
    { key: 'gas_concentration', value: 1040 },
    { key: 'mode', value: 'gas' }
  ],
  deviceId: 'A152',
  type: 'data_bidir',
  timestamp: 1637575251,
  seqNumber: 2,
  _id: '619b6a5bf83148c4cc3ea3b9'
}

So the only difference is the removal of key’s attributes: unit, isCode, _id. 

We have released these new features recently:

• Either WiFi routers or BLE beacons stored in our DB could be available to all devices registered in the platform or only to selected groups
• Full support for SimpleIndustry Legionella specific mode including the calculation of risk level
• Support of SimpleHW analog events to measure the voltage
• Added BLE Beacon support to IET10 parser – you can use device for indoor localisation using BLE beacons
• New version of public dashboard is updated in real-time

We have added a support for new version of AirWits R6.2 from Connected Inventions. Supporting calibration details and CO2 baseline.

From now, we apply the same mechanism as Sigfox – once you register a new device, we store information about the acquired connectivity product but without start-end range. The subscription will stay inactive, you will not see any dates in shopping cart or in connectivity details. Once we receive the first message, we activate your subscription and update start-end range accordingly.

You can now register large number of devices in one batch and the subscription clock will start ticking only after the first message is received, so you will not loose any time from acquired subscription in case there is a delay between device registration and device installation on site.