1

Automation 5.0.4000

Item handlers' inputs

Empty input values were omitted on building LDAP filters, i.e. on empty name input the filter was matching on any name instead of empty item names only. Now it is fixed.

9.0

2

Automation 5.0.4000

Arrays string representation

Java arrays' string representation was the default one that is a non-human readable string. Now it is fixed to be the same as for java collections, e.g. to contain the string representation of each element.

9.0

3

BACnet 1.1.0

Stack initialization

If the binding IP address was not explicitly set in the configuration, the BACnet stack failed to select automatically an IP address from the available network interfaces on the host. Now the stack is initializing correctly.

10.0

4

BACnet 1.1.0

Dynamic configuration update

A synchronization issue occurred in some cases when update the adapter configuration in parallel with the initialization process of the adapter. The exception resulted in failing to apply the new configuration properties and failing to alter the affected runtime behaviour of the adapter by the configuration. Now, the bug is fixed and the configuration process is performed in consistency without any unexpected synchronization issues.

10.0

5

BACnet 1.1.0

Dynamic configuration update

Тhe polling interval for the devices was not changed after configuration update which did not affect the polling mechanism. It kept sending periodically requests at the old time interval. This is now fixed and after update of the polling interval, the requests are sent at the new time interval.

10.0

6

BACnet 1.1.0

Polling requests

The device polling mechanism was not stopped after adapter bundle restart when discoveryAutoAdd property was enabled and it resulted in sending unnecessary polling requests and redundant network traffic. This is now fixed and no unnecessary requests are sent.

10.0

7

Cameras 4.5.1

Status checks

When a camera is unplugged, a status check is performed regularly, to see if it has been plugged back in. Due to a race condition, it was possible to get several such checks in a short period of time, which generated unwanted network traffic. This is now fixed.

10.0

8

Config Tree 2.3.5000

Configuration Admin

There was a rare race condition with configuration becoming bound to Config Tree CM when not bound previously. Now it is fixed in Config Tree CM.

9.3

9

Core 1.4.1000

Change log level

The com.prosyst.util.ref.Log now can change log level through the system properties "logLevel", "logPrintLevel" and "measurements".

9.3.3

10

Core 1.4.1000

Deleting log configurations

The com.prosyst.util.ref.Log now deletes its configurations, if after restarting it finds that the corresponding bundles have been uninstalled.

9.3.3

11

Core 1.4.1000

slf4j Logger configurations

Every call to LoggerFactory.getLogger(...) used to reset the corresponding log configuration to the default INFO level. Now it works properly.

10.0

12

Core 1.4.1000

Starting target image

An error was sometimes logged by the com.prosyst.mbs.core.console bundle when starting a target image. After this log the console stopped functioning. This is now fixed.

9.3.3

13

Device Access 3.6.0

Log

Device Access logged errors when device is adding and bundle is stopping at the same time. Now this is fixed and errors are not logged.

9.0

14

Device Access 3.6.0

UIDs

The DeviceAdmin javadoc is updated that error will be thrown of create operation when provided device UID or device item UID is equal to existing FunctionlItem in the system with the same UID.

9.0

15

FIM 2.3.2000

Groups API stored data

The defined mbs.fim.data.clean.onUnintall system property default value not considered as true if missing. Now is fixed in order to remove the DB stored data by default on group items' bundles uninstall.

9.0

16

FIM 2.3.2000

FIM Web Admin

The item page for a FunctionalItem instance registered after the FIM items table initial load was not opened in cases of new bean references. Now it is fixed with successful metadata load of all related resources.

10.0

17

Externals 1.5.0

HTTP server start

There was a transient NullPointerException which occurred during starting of the HTTP server due to jetty-util. It is now fixed.

10.0

18

Externals 1.5.0

OSGi Log not working

There was a logging error when mBSA was used with java.util.logging, and it was not forwarding to the OSGi log. This was due to Apache Aries Spifly and it was patched.

10.0

19

Externals 1.5.0

Eager class loading in JVM

Apache Aries Spifly was modified so that pre-loading of some classes is done in order to run properly on JVMs with eager class loading.

10.0

20

Externals 1.5.0

Service Loading

Some situations with ServiceLoader usage with classes that were not always available as exported packages resulted in NoClassDefFoundErrors from Apache Spifly when class loading was done. This caused the stopping of the functionality of the bundles. This is patched and now results in WARNING logs.

10.0

21

Externals 1.5.0

ServletContextHelper Service

There was a NullPointerException while unregistering the ServletContextHelper service from org.eclipse.equinox.servlet. This is patched.

10.0

22

Framework 8.6.1000

Framework wiring,
Data transfer objects (DTOs)

Fixed the behavior of Bundle#adapt(FrameworkWiringDTO.class) method when invoked for the system bundle. Now it returns the correct data, which encapsulates the framework wiring.

10.0

23

Framework 8.6.1000

Framework hooks,
Resolving

There was a memory leak, involving bundles registering system event hook(s) and fragments with native code. This issue has now been fixed.

10.0

24

Framework 8.6.1000

Framework storage

There was a problem recovering the bundle state upon framework restart, when bundle was previously installed via specific URL(s)(mprm://). This issue has now been fixed and the framework handles the incorrectly implemented URL handlers.

10.0

25

Framework 8.6.1000

Framework launcher,
Execution environments

There was a problem recovering osgi.ee capabilities when framework is started through a framework launcher with ready storage. This issue has now been fixed.

10.0

26

Framework 8.6.1000

PERC

Framework server startup script for PERC has been adapted to work with latest JVM version 8.3 build #1013.

10.0

27

History 1.4.0

SQLite history entry data

Fixed the broken support of entries with null token values in the default SQLite History SPI.

9.0

28

ONVIF 1.4.0

PTZ Stop Device Access

Executing the PTZ Stop Device Access operation was not working and did not cause an error. Providing the pan-tilt or zoom optional parameter did not affect the operation. Worked fine when it was used from command shell. This is now fixed.

9.X, 10.0

29

OSGI 1.7.1

Status code

Wrong status code was generated when platform state is not ACTIVE. HTTP status code 404 Not Found was returned for missing resources regardless of the platform state. Now, when the platform state is not ACTIVE, status code 503 Service Unavailable is returned.

10.0

30

OSGI 1.7.1

XSS vulnerability

The XSS vulnerability in WebConsole login page, which allowed attackers to inject JavaScript code in 'referer' form parameter, is now fiex

10.0

31

REST 2.1.1000

Swagger versions

Documentation of Swagger documentation generator claimed to support Swagger version 2.0.md and 1.2.md, when it supports version 1.2.md only. This is now fixed.

10.0

32

REST 2.1.1000

Web Services REST kitman script

Missing proper checks on resources caused errors and possibility of resource leaks when uninstalling. The needed checks are added and this is now fixed.

10.0

33

REST 2.1.1000

JAR structure

A few jars had incorrect ordering of the files inside, which was causing signing issues. This is now fixed.

10.0

34

REST 2.1.1000

Kitman script
execution environment

Web Services REST Compact M2M, Web Services REST M2M and all demos had wrong execution environments, causing errors, when trying to install. This is now fixed with adding the correct minimum execution environment for all of the kits.

10.0

35

Scripting 1.0.2000

HTTP demo permission

Due to incorrect permission handling in the HTTP demo it was not working when Bosch IoT Gateway runtime was running with security on.This issue is now fixed.

10.0

36

Scripting 1.0.2000

dumped warning
Nashorn JavaScript Engine

There was a warning that was dumped on system output when Nashorn script engine was used on JDK version 11 and above. The warning is suppressed now.

Nashorn JavaScript Engine is deprecated as of JDK 11 and might be removed from future JDK releases.

10.0

37

Websockets 1.3.1

Connection state

A race condition in legacy WebSocket implementation led to reporting a connection as opened before both client and server sides are ready to use it. This could have caused errors when an attempt was made to send a message before the connection was fully established. This issue is now fixed.

10.0

38

Websockets 1.3.1

Connections count

In legacy WebSocket implementation connections count was not updated when session expired, which caused the maximum of opened connections to be quickly reached. After this point the client was not able to open new WebSocket connections. This is now fixed.

10.0

39

SHIP 2.4.0

SHIP connection state

A ConcurrentModificationExcetion was thrown when internally checking SHIP connection state when the underlying websocket connection was actually closed. This might result in an unexpected reported state for a SHIP device. This is now fixed.

10.0

40

TEE 2.0.5000

JUnit5

TEE now installs Junit 5 by default, because it does no longer use java packages (javax.lang.model) that are not available in JavaSE 8 compact 1 and 2 profiles.

10.0

41

Zigbee 4.9.0

Manufacturer specific responses

Sending wrong ZCL (Zigbee Cluster Libarary) manufacturer specific responses to devices. The manufacturer code was not used when sending messages via AbstractDeviceClassObjectV3#sendZCLResponse(...). Now this problem is fixed and correct manufacturer specific messages are sent.

9.X, 10.0

42

Zigbee 4.9.0

Device functional items

If a device with IASWarning functional item is not reachable on framework restart or after backup and restore, there would be a NullPointerException. As a result no items would be registered for the device functionalities. The problem is fixed and all functional items are registered.

9.X, 10.0

43

Z-Wave 6.1.0

Battery-powered devices
configuration

Battery-powered devices already included in the controller network before starting the Z-Wave stack were not getting configured and associated even after the device sends a Wake Up Notification. This is now fixed.

9.0

44

Z-Wave 6.1.0

Door Lock Operation,
Door Lock Configuration
reports

Unsolicited Door Lock Operation and Door Lock Configuration reports in HDM Adapter were not handled properly in the DoorLock device class instance. As a result, both corresponding properties were not updated as expected. This is now fixed.

9.0

1

mBProfiler 6.4.6000

Text is incorrectly visualized when Windows 10 display scaling is other than 100% in Bosch.IO Setup Tool.

2

ONVIF 1.3.0

ONVIF Discovery is not detecting devices if the local network IP is changed during runtime or by DHCP, therefore the discovery is no longer working, until the ONVIF Core bundle or the framework is restarted.

3

ONVIF 1.4.0

In Backup Restore, restoring ONVIF device from 10.0.0 to 10.1.0 registers Firmware Update Item with wrong tag for RCP+. If Firmware Update process is started and completed, the Functional Item is getting the right tag for ONVIF. This is valid only for non-Bosch cameras.

4

ONVIF 1.5.0

The ServiceID of the functional item for RCP+ firmware upgrade is changed.
The old serviceID was DeviceService which was causing conflict with the other DeviceService items. That was due to the lack of guarantee that each UID belongs to the same functional item, if the order was changed during functional item registration.
To escape the conflict, a unique serviceID was provided for the RCP+ firmware update: RcpPlus.
Examples of UIDs:

• for 10.0.0 and 10.1.0 releases
  da:item:ONVIF:Bosch-FLEXIDOME_IP_5000i_IR-094456675477890014/DeviceService/2:FirmwareUpdate ()
• for 10.2.0 release
  da:item:ONVIF:Bosch-FLEXIDOME_IP_5000i_IR-094456675477890014/RcpPlus/1:FirmwareUpdate ()

This change is backward incompatible for 10.0.0 and 10.1.0 releases.

5

Z-Wave 6.1.0

While using the ZIP Gateway based driver, DA and HDM devices stay online even if they are not accessible in the network anymore.