API returns 400 Bad Request for certain /api/status calls

[oh2th]

I develop the app for Athom Homey homeautomation and while developing I found an issue with API calls:

• A query to get everything /api/status returns the full JSON, but with HTTP 400 Bad Request
• A filtered query for /api/status?filter=sse,fna,car,alw,acs,frc,trx,cards,err,wh,pha,nrg,eto,tma,amp,ama,cbl,fsp returns the filtered JSON, but with HTTP 400 Bad Request
• A filtered query for /api/status?filter=sse,fna,car,alw,acs,frc,trx,cards,err,wh,pha,nrg,eto,tma,amp,ama,fsp returns the filtered JSON, with HTTP 200 OK

So full status query and queries that have filtered API keys not supported by the device such as CORE and PRO not having the cbl available results in HTTP 400 Bad Request. This in turn results the http client to fail and fails the process in the application as HTTP errors are traped and through an error.

Tested on go-eCharger PRO with 60.3 firmware.