Bosch IoT Manager
The new Bosch IoT Manager service release comes with various improvements:
Provided common gRPC endpoint
Users can now access Device Inventory and Mass Management Engine methods via a common address. The value https://grpc.manager.eu-1.bosch-iot-suite.com/ 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, com.bosch.iot.dm.event.EventService can no longer be accessed via gRPC. Any obsolete classes have been removed from the remote libraries and the Javadoc.
In addition to the listing event subscriptions methods provided in the Device Inventory API in 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 events had to be then filtered against the rule scope. This resulted in transferring 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.
Fixed the bug causing failure to fire rules with event triggers where the event concerns the adding or editing of a feature.