New features on Notification dashboard

/in , /by

Added new features:

  • Filter by day / month or time range
  • Export to CSV and Excel
  • Possibility to add a comment to every notification

Electricity consumption with SENSECOM-OMD-E

/in , /by

We have added a support for new electricity consumption monitoring device from SmartImp. SENSECOM-OMD-E is reading the registers directly from electricity meter via optical sensor. The installation is super easy, you just attach device via magnet and press one button. More information about device is available here.

Support in IO Frog:

IOTA CO2 support

/in , /by

Added support for new CO2 sensor from IOTA

Export of devices to CSV/XLSX

/in , /by

You can export of all devices from Group Manager, tab Devices:

  • You can choose exporting devices from the current group OR the current group including subgroups
  • You can export to CSV or XLSX
  • We added an info of subscription end to exported file
  • Exporting reflects the filter params, so you can export devices to be expired only for example 

New set of features and bug fixes

/in , /by

We deployed several improvements recently:

  • Support for Leak Rope devices from SimpleHW
  • Current group is being opened in Group manager instead of root group
  • Mapping of beacon IDs to devices statuses
  • Improved data types in notification setup
  • Fixed CI CO2 parsers (header information)
  • Public dashboard small fixes
  • Selected main key is being displayed in table dashboard in Last message column
  • Selected keys applied on Facility monitoring dashboard
  • Possibility to use Combain geolocation services in WL solution
  • Improved logging of data forwarding
  • SimpleHW API 6 – improved support for 2 MAC addresses
  • Fixed sorting in Table view
  • Fixed search with special characters in device name

Example of device filter by current value

/in , /by

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

/in , /by

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

Several major changes and new features released today!

/in , /by

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

/in , /by

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

Optimisation of the structure of forwarded messages

/in , /by

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.