This offer is only addressed to commercial customers including freelancers and entrepreneurs. All prices are exclusive of value added tax (VAT).
  • Share via email
  • Subscribe to blog alert

Bosch IoT Manager: common gRPC endpoint provided and various improvements

The new Bosch IoT Manager service release, available through Bosch IoT Suite for Device Management, comes with various improvements:

Common gRPC endpoint

Users can now access Device Inventory and Mass Management Engine methods via a common address. The value is common for both gRPC-related variables.

Dedicated Event Service APIs added

The Device Inventory and the Mass Management Engine now provide a higher-level API for working with subscriptions. As a result, can no longer be accessed via gRPC. Any obsolete classes have been removed from the remote libraries and the Javadoc.

In addition to the methods of listing event subscriptions provided in the Device Inventory API via our previous release, the following new methods have been introduced in the Mass Management Engine API:

  • List Rule Events Subscriptions
  • List Task Events Subscriptions

See the Bosch IoT Manager Javadoc for more information.

Event subscriptions are now visible by serviceInstanceId

Every user authenticated with a token having a particular serviceInstanceId is now able to access (get, list and remove) all event subscriptions made within that service instance. This is possible even if the event subscriptions have been created by this or another subject (i.e. user or application).

Enhanced behavior of rules with device event triggers

The current improvement allows users to understand early on if they have provided any improper definition of a device event trigger for their rule.

The validity of the trigger definition is now checked upon the enablement of the respective rule and in case of any problem, the rule will not be enabled and will throw an error. Thus the user will know of the problem immediately and will be able to make the necessary adjustments.

Improved efficiency through single-device listeners for single-device rules

Until now, rules whose scope involved only a single device received events for all devices in the service instance, which then had to be filtered against the rule scope. This resulted in the transfer and processing of lots of unnecessary event information. The current improvement adds support for single-device listeners where rules happen to involve only a single device.

Bug Fixes

  • Fixed a bug causing failure to fire rules with event triggers, where the event concerns adding or editing a feature.