Crashes when wrong identifier assigned

There's an odd issue showing-up in the logs. It seems an unrelated issue, is triggering the error that reminds of registration.

Feb 29 18:21:00 vhh.gateway-VANILLA bcms-daemon[2967]: 2024-02-29 18:21:00 - bcms.api - INFO: Loading API with identifier vhh-server ...
Feb 29 18:21:00 vhh.gateway-VANILLA bcms-daemon[2967]: 2024-02-29 18:21:00 - bcms.main - ERROR: Failed to load backend api. Is this device registered?: 'data'
Feb 29 18:21:01 vhh.gateway-VANILLA systemd[1]: bluetooth-client-manager.service: Main process exited, code=exited, status=1/FAILURE

This issue only seems to occur with command line arguments:

/srv/.vhh-profiles/gateway/packages/bin/bcms-daemon --use_device_identity True --application_identifier vhh-server --username default --notify False
2024-02-29 18:27:32 - bcms.api - INFO: Loading API with identifier vhh-server ...
2024-02-29 18:27:32 - bcms.main - ERROR: Failed to load backend api. Is this device registered?: 'data'

The issue is related to a wrong application identifier. I should be using vhh instead of vhh-server. This needs to be handled better. It's not important, as long as the correct identifier is assigned, but it should be handled better.