Indirect Asset Tracking with the DeepHub - The simple, elegant and cost-effective asset tracking solution

Consider a typical warehouse where all your workers are equipped with a barcode scanning device. These devices typically have an embedded Android smartphone, therefore the DeepHub Kiosk UI can run on them out-of-the-box. Conveniently, the Kiosk UI now includes barcode scanning functionality as well. Scan a barcode and if an asset, A.K.A a trackable, is not found, simply create one with one tap of your finger. Now let's consider that you invested into a locating system but don't want to attach a tag to each asset because that would be costly (assuming you have thousands of assets in your warehouse). Instead, just have every worker wear a tag while working in the warehouse. Within the Kiosk UI, a tag, A.K.A a location provider, can be paired with our Kiosk UI instance, ensuring the position of the worker's tag becomes the position of the Kiosk UI. When a barcode is scanned, the position of your device can be used and associated with the scanned asset, ensuring the asset gets a location. That's it. With just a handful of tags for your workers, all your assets can be tracked.

DeepHub 2023 R2 - 2.4.0 was released today!

One noteworthy change is a new property for trackables that allows their participation in collision handling to be enabled or disabled. Not only can this significantly save CPU power if collision handling is not needed, but it also allows for easy handling of use cases where a huge amount of tracked assets are close to each other, resulting in a bulk of collisions happening at the same time.

Example: a forklift moves a pallet with a lot of RFID-tagged assets. All these assets are within close proximity to each other while they reside on the pallet. They are colliding but the information that this is happening is not relevant. Collision handling for the forklift itself is nevertheless very relevant and so the trackable representing the forklift has the option to "participate in collision handling" set to true, while it stays off for all the RFID-tagged assets on the pallet. Only collision events for the forklift would be delivered to listeners subscribed to these events.

Have a look at the changelog for all the details.

The omlox v2 specification was finalized and approved. It contains many enhancements to the "omlox core zone" and the "omlox hub". The former now complies to IEEE 802.15.4z, offers a new "Uplink-Time Difference of Arrival (UL- TDoA)" mode, and supports UWB channel #9 (~8 GHz) - allowing for global coverage, as this is currently the only channel that can be used worldwide without any local restrictions.

The omlox hub specification v2 includes a "rule engine" (the DeepHub has had a Locating Rule Engine for over a year), support for uninitialized zones, a "fence_timeout" property for trackables and location providers to overrule timeout settings of a fence, and several new REST API endpoints for greater convenience.

A bit of marketing for the changelog of the DeepHub, which can be found here: changelog. It contains the changes made in every version of the DeepHub and not only the one for the specific version that you have currently selected here on this documentation page!

The new release DeepHub 2023 R1 - 2.3.0 was released today!

Have a look at the changelog to get an idea of the features and bug-fixes that have been incorporated into this version.

Welcome to the new DeepHub docu page. We switched to a new docu framework called Docusaurus and it works like a charm.

One of the main interesting features of Docusaurus for us, is to be able to easily host documentation for several versions of a product. Therefore we incorporated this feature to provide the DeepHub documentation for the latest stable version, currently the DeepHub 2022 R2 - 2.2.3, as well as for the upcoming release at the same time. To switch between the different versions, just use the pull-down menu on the top-right of this page.