October 16, 2024

Mobile app reworked

The Sensolus mobile app has been extended and the user experience is optimized. The documentation of the mobile app is also added to the documentation center.

Mobile app notifications: sensor values added

The alert notifications on the mobile app from sensor value alerts will from now on also show the temperature itself.

Performance improvements for geozone visit reports and related views and geozone visit recalculation (important when editing geozones!)

This is a somewhat technical improvement that requires some deeper explanation.

Why? Some experienced users might have encountered already the following: Just after adding a new geozone, you see that geozone appears in the single tracker location geozone visit history tab. But when you go to the geozone inventory, the history is not updated. That's confusing, right?

Before this release, some screens and reports were always re-evaluating the complete geozone visit history on-the-fly, starting from the location history of each asset (for example, a single asset geozone visit history tab). Calculating on-the-fly is fast for one asset, only for the last week or 30 days, but does not scale well when doing fleet reporting. So, the geozone visit report, which was also calculated on-the-fly, was often very slow to generate. Other screens, like the geozone inventory graph, were based on database-persisted geozone visit record - which is very scalable.

With this release, all views and reports that contain historical geozone visit data, are based on database-persisted geozone visit records.

The benefit: No more inconsistencies between different views. The reports using geozone visits are generated faster. Also, in the geozone visit report, the rather confusing concepts of 'entry time exact' and 'exit time exact' can be forgotten about (these columns will be fully removed in a later release).

There is a catch, however. For obvious performance and server load considerations, the platform never automatically recalculates all historical visits, whenever someone makes any change to a geozone (add or edit) (because this would require always processing the complete location history of all trackers in the organization).

Instead, it is expected that you manually trigger a recalculation of geozone visits, after having made your geozone changes. This can be performed using the new 'geozone visit recalculation' bulk operation for trackers. This is explained here Asset geozone visits recalculation when editing geozones. There is a limit to how many times you can recalculate per organization, to avoid improper use (we'll monitor how often this is needed and adapt the quota to reasonable use cases).

New dashboards widget: location history

The location history is added as new data source in the dashboards.

Sometimes it is useful to know where assets have been over a period of time without needing to click to all individual assets. Seeing all asset points and their locations over time let you do this. This can help to for example see where it is useful to create new geozones. It can also be used to spot strange Wi-Fi jumpers and to take them out.

Refined shock detection UI

Some small updates are made to the UI of the screens related to shock detection. This will make the interpretation of this screens easier.

Optional time range added to diagnostics API calls

The diagnostics API has been extended with an optional time range.

Optimization visualization device messages

The device messages visualization have been optimized to make them easier to read and understand.

Not all customers have access to the devices messages, this is only made available on request.

Optimization asset detail page when asset is 'not activated'

The asset detail page of assets that aren't activated yet is now made easier to understand. Some visuals are added and some irrelevant information is taken out.