Example of device filter by current value

For your inspiration: you can filter devices by CO2 level and list all devices in specific group with CO2 > 1000ppm:

More options in selection of devices based on platform expiration date

You will find more options in selecting devices by platform expiration date:

Several major changes and new features released today!

We have deployed several major changes / features today:

  • As we have already informed you in previous post, there are some minor changes in forwarding. Please, read the article if you are using this feature.
  • We offer more robust processing of incoming messages now for large customers. The mechanism is storing the messages in the AWS queue running in high available mode. If we need to do some major maintenance that requires stopping our application servers or DB servers, the messages will be stored in the queue until the maintenance is finished. The messages will then be automatically processed. Utilisation of this mechanism require different callbacks. Please, contact us if you are interested in this feature.
  • Data you see on the dashboard is not tightly linked to data received in the last message. The concept of tracked keys was completely refactored:
    • You do not have to choose tracked keys in device settings from now. We store the latest value of all data with the appropriate timestamp on device level automatically on all devices. For example, if your device had sent a firmware version in the first activation message one year ago, it will be automatically stored here.
    • You can see the latest value of all device data in Data details > under Last status tab. This page is empty until the device sends the first message since the time of deployment of new release. You will find the timestamp of every latest data value here as well, so you know when the specific data was updated.
    • And even more, you can filter devices by such value on the main dashboard using the new Filter by option in search bar. For example, you can filter devices that have the latest CO2 level above 2000ppm. At this moment you can search only by Metric system units.
  • You can choose what data you want to see on the dashboard in device Settings > Custom view > Dashboard data. We have preset the list of dashboard data based on formal tracked keys preference for you convenience.

This release required many deep changes in our system and even we tried to test it as much as possible, you may spot some issues. Please, do not hesitate to contact us in such case. We will do the best to fix them as soon as possible.

XLSX export

You can choose if you prefer CSV or XLSX format of exported data now.

Optimisation of the structure of forwarded messages

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. 

Set tracked keys for multiple devices

If you need to set tracked keys for multiple device, go to Group management, tab Devices and set tracked keys for selected devices in one step!

New features released

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

More convenient URLs

We had an idea to have only one base URL at the beginning (iofrog.com) but since we use different technologies for app development and different for web site development, we needed to create www.iofrog.com and iofrog.com. This became confusing over time and thus we have decided to make it better.

  • app.iofrog.com will be a base URL for the app (current www.iofrog.com)
  • iofrog.com will navigate you our informative / documentation site (current iofrog.com)

The app is already accessible at app.iofrog.com from now. Please, start using this URL. www.iofrog.com will navigate you to documentation site soon. We have added a new CONNECT button to navigate you to the web app.

We believe this naming will be more convenient for you and for all new partners and users.

Added support for new AirWits CO2 R6.2

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

Upload photos of device installation

For better support, you can upload jpeg/png images up to 1MB to every device to keep pictures of how your device is being installed. Go to main dashboard and choose Documentation from device menu:

You will find a new dialog allowing you to upload multiple photos (in case you have device update permissions):