BleBox Hubitat Integration: Cannot get property 'value' on null object

[SplatManDK]

After resetting my Hubitat and re-installing everything from scratch I am unable to add my BleBox SwitchBox D device. After installing the App and Driver as per instructions, I add the device with the app. The App finds the device (though not every time) and after adding it in the drop-down, the App then returns to the App main page in Hubitat with no further input. Subsequent attempts to open the BleBox Integration app now results in the following UI error:

Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.

The contents of the Log is the following:

app:372025-01-04 01:31:37.306 PMerrorjava.lang.NullPointerException: Cannot get property 'value' on null object on line 182 (method mainPage)
app:372025-01-04 01:31:37.280 PMdebug2.1.0 addDevices: Devices = [:]
app:372025-01-04 01:31:37.260 PMdebug2.1.0 initialize
app:372025-01-04 01:31:37.256 PMdebug2.1.0 mainPage

[SplatManDK]

Additional information:

I am able to control the BleBox device using the dedicated Android app
The device is updated to most recent firmware
Hubitat is updated to most recent as of Jan. 4th 2025 (2.4.0.145)
The Hubitat device is Elevation C8 (non-Pro)
The network currently used is 10.30.0.0/16 (it has internet access but is isolated otherwise)

[SplatManDK]

Additional information 2:

Wife works with DevOps and just so happened to be able to read Groovy, but without knowing a single thing about hubitat. Her analysis is the following: The API of the SwitchBox D device reports it's device type as "bleBox switchBox" but this does not match any entry in the "davegut" namespace, which seems to contain a list of known BleBox device types.

The specific error she produces after messing around with the code is the following:

[com.hubitat.app.exception.UnknownDeviceTypeException: Device type 'bleBox switchBox' in namespace 'davegut' not found]

The conclusion is probably that BleBox has, again, made a breaking change to their API in the latest firmware.

Honestly, I feel BleBox has become a bloated mess of mandatory cloud-stuff and phone apps. They developed delusion of grandeur and want users to put everything into their own ecosystem - completely ignoring users who used their products in mixed environments. This is the fourth time after purchase that something breaks. Even with a DevOps wife, the WAF is under pressure for all of this. I'll probably swap the device for one or to SONOFF units and be done with it.

[SplatManDK]

Ok, so the namespace is apparently the sum of BleBox drivers installed. Thus, installing the driver for the single-channel BleBox device enables me to control one channel on the device.

Root cause seems to be that BleBox has decided to make the SwitchBoxD device report itself as "SwitchBox" where it was previously "SwitchBoxD". I assume they now differentiate their devices using other properties than the name, in their own software.

Conclusion: Yep, BleBox did indeed make a breaking API chance. Again.

Some changes to the SwitchBoxD and SwitchBox drivers in Hubitat might be necessary, as they will now be identified as the same device. The drivers will have to be consolidated, and the presence of two channels must be rewritten.