DeepHub® 2023 R1, 2.3.0
[Core] Added new API targets
[Core] Previously ambiguous API http error codes are now clearly distinguishable by their error types. This introduces a new format for error types, following a reverse url scheme. Examples for such error types are
[Core] If a trackable has a trackable motion its location is now also considered as the significant location for the API endpoint
[Core] Added ARM support.
[Core] Added parameter to filter fence events by object_type (one of
[Core] Consumption objects now contain the size of a zone.
[Core] Added object change events to websocket to inform clients about new, modified, and deleted objects.
[Core] Added the number of (active) location providers grouped by type to the consumption report.
[Core] Updated error handling for Cassandra databases.
[Core] Only for API version 2 fence events now always contain the associated provider id for the location update which triggered the event.
[UI ADMIN] Allow to search for custom properties content as well in filter UI and list of fences, zones, trackables and location providers.
[UI KIOSK] Added new UI mode 'kiosk'.
[UI KIOSK] Added min. (DEEPHUB_MAP_MINZOOM) and max. (DEEPHUB_MAP_MAXZOOM) zoom to environment variables.
[UI KIOSK] New default for the max. zoom becomes 24.
[UI KIOSK] Added scale control.
[Core] Fixed a bug, where zones with invalid local coordinates were rejected, but still written to the database.
[Core] Fixed a bug, where timestamp_generated could not be set to
[Core] Fixed course of location.
[UI ADMIN] The 'name' field is not required for trackables, location providers, fences and zones anymore.
[UI ADMIN] The minimum number of characters for the 'name' field is now 1 for trackables, location providers, fences and zones.
[UI ADMIN] Fixed searching for id and name content in list of trackables and location providers.
[Core] Removed property
[UI] Renamed environment variables from DOCKER_ to DEEPHUB_.
DeepHub® 2022 R2, 2.2.3
[Core] Added new configuration parameters
[Core] Fix error handling for rate limit errors for Amazon Keyspaces and Azure Cosmos DB.
[Core] Fixed count of active trackables and location providers for consumption reporting.
DeepHub® 2022 R2, 2.2.2
[Core] Added Cassandra support for Amazon Keyspaces and Azure Cosmos DB.
DeepHub® 2022 R2, 2.2.1
[Core] Fixed a bug where duplicated data might accumulate in a Cassandra database. An affected database will be cleaned during the first start of this version.
DeepHub® 2022 R2, 2.2.0
[Core] Optimized internal event handling.
[Core] Added the API endpoint /license/key, to be able to update the key via an API call.
[Core] Improved the restart behavior of DeepHub by restoring event timers based on the most recent persisted locations. Events in intermediate states, like tolerance areas or exit delays, are not restored.
[Core] Added DeepHub API version 2 for all endpoints, implementing a preview of omlox™ API version 2. If authentication is used, the permission.yaml needs to be updated for the new /v2/ targets to be accessible.
[Core] Added the possibility to POST entities with a given id (i.e. without DeepHub generating a new id). This is only available for endpoints residing under API version 2 (e.g. /v2/zones).
[UI Admin] New configuration menu: zones and fences live there now. The current subscription/license information can be found there as well.
[UI Admin] New URL parameter to pan & zoom directly to trackables and/or location providers and to filter/show only the onces mentioned as parameter
[UI Admin] The “transformation” button on the first page of the zone creation dialog got removed: it was UX-wise not obvious what it does and typically never used because working with a zone implies the use of a transformation of coordinates.
[UI Admin] The UI docker image is now based on the nginx-unprivileged base image thus allows to be used in restrictive kubernetes policy environments. The web server serving the UI therefore now runs on port 8080 which has to be taken care of in e.g. docker-compose.yml files orchestrating the DeepHub and its UI container.
[Core] Fixed a bug where TrackableMotions could remain when the associated Trackable was deleted.
[Core] Fixed a bug where circular fences could not be posted.
[Core] Fixed an issue where under extreme load conditions some events would not be forwarded through the websocket interface.
[Core] Fixed a bug where stationary trackables were not listed after a restart.
[Core] Fixed a bug which could lead to database corruption with sqlite3. The database file is therefore migrated to a new version. Furthermore, the database file is renamed to
[Core] Fixed an issue with temporary files from sqlite for read-only Docker containers. For these, it is required to set the environment variable SQLITE_TMPDIR to a writable folder, e.g., the mounted folder with the sqlite database.
[UI Admin] Filter toggle button immediately opens up the advanced filter dialog instead of the hard to use “right sidebar”
[UI Admin] On touchscreen devices, tapping on a trackable or location provider to get detail information as tooltip did not work
[UI Admin] Importing of custom properties of zones did not work: they got removed
DeepHub® 2022 R1, 2.1.1
[Core] Enhanced the performance of SQlite operations.
[Core] Fixed a bug where subsequent location updates were rejected if their distance was close to floating point precision.
[UI Admin] Allow to use separate image files as site map per floor level.
DeepHub® 2022 R1, 2.1.0
[UI Admin] Allow to use an image file as site map. On top of the map or as replacement of the latter.
[Core] Fixed a bug where event timers were not correctly removed.
[Core] Removing a colliding trackable via the API now triggers a collision end event.
[UI Admin] Unable to edit properties of a fence within the UI.
DeepHub® 2022 R1, 2.0.0
[Core] Added a rule engine with locating rules and the API endpoint /trackables/rules/locating.
[Core] Added a validator API /validator/rules/locating to check rule expressions.
[Core] Added Cassandra support.
[Core] Added new configurable parameter
[Core] Transformations to EPSG:32661 (UPS north) and EPSG:32761 (UPS south) are now supported.
[Core] DeepHub now aborts starting without a stack trace, presenting the underlying error message more prominently.
[Core] A location without a timestamp_generated will default to
[Core] Outdated location updates no longer produce trackable motions.
[Core] Added support for ISO-24730 based RTLS systems.
[Core] Added health API endpoints: /health, /health/system, /health/ws, /health/zones/summary, /health/zones/:zone_id, /health/sources/summary, and /health/sources/:source_id.
[Core] Changed docker base image to Ubuntu version 22.04.
[UI Admin] New color theme for UI
[UI Admin] New UI for usage of location providers
[UI Admin] Make DeepHub UI docker container usable in read-only mode
[UI Admin] Support fence definition with negative local coordinates
[UI Admin] Use vertical color bar to mark different fence event triggers in different colors
[Core] Fixed Trackable Removal Events.
[Core] Fixed timestamp for GeoJSON locations.
[Core] Fixed trackables id array for GeoJSON locations and fence events.
[Core] Fixed a memory leak when assigning an empty string to the properties member of a location.
[UI Admin] Check timestamp during updates to avoid usage of outdated information
[UI Admin] Two
[UI Admin] Crash in UI when using a semicolon in search bar of live view
[UI Admin] UI is unable to work with zones and fences without names
[UI Admin] UI for fence editing overwrites z-coordinates of corner points on backend
DeepHub® 2021 R2, 1.3.1
[Core] Updated error handling for environment variables.
DeepHub® 2021 R2, 1.3.0
[Core] Added auto-zone-extension (APE) feature to the zones API, allowing to automatically update mobile zones.
[Core] Added API to query trackables which are considered within a given fence according to their last reported location.
[Core] Added fine grained permission management for WebSocket subscriptions and messages. Refer to the Security & Authorization documentation for details.
[Core] Added the ability to configure via environment variables.
[Core] Added new parameter
[Core] Implemented coordinate transformations for endpoints which were missing these options.
[Core] Added new /trackable/:trackable_id/fences API endpoint. This returns the list of fences which contain the given trackable.
[Core] The file hub_config.yaml will no longer be created by default. Instead an example file is included in the bundle. Also, an empty configuration file no longer causes problems.
[Core] Added API to query motions which are considered within a given fence. (/fences/:fence_id/motions)
[Core] Added new parameter
[Core] Added optional boolean property
[Core] Added new parameter
[Core] DeepHub now enforces the restriction that proximity zones must not have ground control points.
[Core] Added the API endpoint /license/info to retrieve license information and warnings.
[Core] The value
[Core] Added the API endpoint /license/info to retrieve license information and warnings.
[Core] The respective
[Core] Updated the Cisco CMX Location Notification endpoint to accept both PUT and POST requests.
[Core] Added support for https communication via proxy servers by configuring the environment variables
[UI Admin] New checkbox in UI (
[UI Admin] New property
[UI Admin] Check if providers of trackable still exist.
[UI Admin] Support for
[UI Admin] Show only one tool tip containing provider and trackable information at once.
[UI Admin] Support
[Core] Fixed handling of infinite fence timeouts
[Core] Fixed z coordinates being lost for invalid but repairable polygons.
[Core] Fixed READ_OWN permissions for summary and root REST endpoints (e.g. /fences and /fences/summary) in case authentication is used. The returned lists are now filtered based on the roles ownership.
[Core] Fixed handling for erroneous consumption reporting.
[UI Admin] Editing a point of a fence does not work.
[UI Admin] Missing
[UI Admin] Icons illustrating the technology in-use are missing in Firefox.
[UI Admin] Unable to remove non-existing location provider from trackable.
[UI Admin] Parameterization of links to DeepHub UI are not working with auth service.
DeepHub® 2021 R1, 1.2.1
[Core] Corrected mismatch to spec:
[Core] Fixed return code handling for consumption reporting
DeepHub® 2021 R1, 1.2.0
[Core] Added filter and transform functionality to WebSocket subscriptions. Please refer to the WebSocket API documentation.
[Core] Internal changes and improvements related to event processing.
[Core] Added consumption and usage statistic API.
[UI Admin] Choose the mapping service
[UI Admin] Missing tooltips for control widgets of map
[UI Admin] Creating two Zones or Fences not working
[UI Admin] Fences: Search not working
[UI Admin] Pressing return key to complete change of a value results in custom properties dialog
[UI Admin] Selecting a fence on the map is not reflected in left view
[UI Admin] Reset zoom level not working if no data is in DeepHub®
[UI Admin] UI stores entered information even though it was rejected
[UI Admin] Fence creation fails in case properties are involved
DeepHub® 2021 R1, 1.1.9
[Core] Log IP address in HTTP and WebSocket handlers on error.
[Core] Added /health API for health checking
[Core] Added a new special role named guest. This role allows to bypass authorization when assigned to endpoint in the permissions settings (e.g., for the /health endpoint).
DeepHub® 2021 R1, 1.1.8
[Core] Updated Zone and Fence API to include exit delay.
[Core] Reject erroneous Trackable configurations with duplicate provider ID references.
[Core] Added trackable_motions:geojson topic to subscribe to geojson encoded motion updates.
[Core] Updated WebSocket session idle timeout configuration.
[UI Admin] Rework of map
[UI Admin] Enable RFID and iBeacon Zones
[UI Admin] Trackables
[UI Admin] UI/UX fine tuning
[Core] Fixed TrackableMotion does contain a point geometry instead of a polygon in case the Trackable does not define a radius.
[UI Admin] Zone & Fence: Fix New dialog next button
[UI Admin] Zone & Fence: Fix editing on map
[UI Admin] Zone & Fence: Fix reset of point fields
[UI Admin] Zone & Fence: Fix Cancel behavior for Edit mode
[UI Admin] Zone & Fence: Fix closing behavior of detail panel
[UI Admin] Live: Fix Search list with multiple location provider
[UI Admin] Live: Fix 401 error on get trackables/motions
[UI Admin] Live: Fix showing trackables with point geometry
[UI Admin] Global: Adopt all units according to spec
[UI Admin] First public release.
[Core] Fixed an issue caused by an external library where the docker container might get into a startup loop.
[Core] Fixed an issue where trackable motions did not get certain values assigned from the related trackable.
[Core] IMPORTANT CHANGE: The /v1/zones API was adapted to the latest version of the omlox™ specification. Most importantly, proximity based positioning systems (RFID or iBeacon) require the position to be defined when creating a zone, while ground control points must not be set. The position was previously optional, which allowed to create invalid proximity zones. For other types of RTLS systems ground control points are still required, and the position is still optional.
[Core] IMPORTANT CHANGE: The property collision_tolerance in the Trackable object has been renamed to exit_tolerance in the latest version of the specification, aligning property names between omlox™ Fences and omlox™ Trackables. This implementation of the Hub has been updated accordingly and may require to adapt the name of this property for client requests.
[Core] Added REST endpoints for handling omlox™ proximity events at /v1/providers/proximities and /v1/providers/:provider_id/proximity. Proximity events allow easier integrations of proximity based positioning systems (e.g. RFID or iBeacon). A proximity positioning system simply sends an omlox™ Proximity object and the Hub resolves the proximity information into a location by referring to the position defined for the zone which relates to the proximity positioning system.
[Core] Added REST endpoints to request trackable motions at /v1/trackables/motions and /v1/trackables/:trackable_id/motion.
[Core] Added WebSocket pub/sub topic trackable_motions according to the omlox™ motion specification. This topic provides real-time updates for trackable movements, also considering the trackable's shape.
[Core] Added Hub configuration option persist_locations which enables to persist all location updates to the database. Previous locations will be loaded when the Hub starts. This option is now enabled by default. Please note that persisting locations affects overall performance.
[Core] Updated several configuration options.
[Core] Updated parsing the elevation_ref parameter of an omlox™ Location object according to the specification.
[Core] Fixed an issue where a wrong crs was displayed in the location object for a certain API request.
[Core] Fixed an issue where a trackable was not correctly removed from the spatial index after it was deleted.
[Core] Updated RPC support. See RPC Interface.md for documentation and usage.
[Core] Updated the admin frontend, added new features.
[Core] Updated trackable and collision API. See the api_draft folder with documentation and examples.
[Core] Added query parameters to conveniently update and select location and fence objects in various projections (local coordinates related to a zone, GPS and UTM projections supported throughout the API).
[Core] OpenID based authorization and Role Based Access Control (refer to Security Authorization.md)
[Core] Added admin frontend to /v1/web
[Core] Flexible server configuration options (refer to Server Configuration.md)
[Core] Fixed: Provider type was always
[Core] Added trackables array to location object. This allows to identify to which trackable(s) a location update belongs to for example for websocket location update subscriptions.
[Core] Added properties field to trackable object. This allows to add custom information associated to a trackable.
[Core] Improvements and fixes to the GeoFence engine.
[Core] Support for customizable IoT Sensors data:
[Core] Added properties to allow fine grained event controls to the Fence object:
[Core] Added params member to Websocket Subscribe request object to allow for parameters related to websocket subscriptions (e.g. crs and geojson parameters, same as query params available for location and fence REST API).
[Core] Basic Authentication and Security Support
[Core] Advanced 3D fence events and general improvements to fence event API. Fence events can now also overlap.
[Core] Added properties to Provider and Fence objects, allowing applications to set generic data.
[Core] Forward properties with FenceEvent, allowing applications to act on associated events (e.g. easily build a relationship between a MES production step and a fence event).
[Core] Fixed an issue when requesting GeoJson objects where the object might be invalid.
[Core] Added Websocket publish / subscribe API /ws/socket for location updates and fence events. Available topics: location_updates, location_updates:geojson, fence_events, fence_events:geojson.
[Core] Added parameter
[Core] Extended /trackables API. You can now create a trackable and locate the most recent location(s) of any of it's assigned location providers via /trackables/:trackable_id/location(s)
[Core] Changed position type in Location object to use a GeoJson Point geometry. This simplifies the API and avoids use of differing geometry types in other parts of the API.
[Core] Updated /providers API
[Core] Improved data persistence
[Core] Added HTTP DELETE method to all API resources to clear current data
[Core] Added /zones/:zone_id/transform and SimpleTransform object specification to allow easy zone setup workflows (useful for example for RFID zone setup to locate scanners)
[Core] Added /fences/:fence_id/events API to generate FenceEvents via API instead of location based fence event generation by DeepHub. This may be useful for RFID scanners or general applications where a 3rd party server may generate its own fence events. This allows to use foreign generated fence events with a DeepHub fence to relate fence events to real world places.
[Core] Added /zones/:zone_id/createfence to allow easy creation from an approximated polygon of an existing zone definition.
[Core] Improved handling of invalid fence geometries and give more detailed error descriptions to a user for invalid geometry data.
[Core] Fixed geometry type definition for the fence region in the OAS specification and updated example data accordingly. Also provided more detailed description of Position, GeographicPoint and GeographicPolygon types.
[Core] First public release