/api/custom show {} if no Custom Entities configured instead of an error

[proddy]

Discussed in #1294

^{Originally posted by harvey637 September 14, 2023}
Hi,
the iobroker adapter for ems-esp requested until v 2.4.0 for "custom" entities,
I guess, that the resposnse to that request somehow changed with the "new" 3.7.0-dev0,
at least I did not spot the logging of this error before.
In the ems-esp-iobroker-adapter this was remedied with introducing v2.4.1 with the switch to turn on/off the call for custom entities.
tp1de/ioBroker.ems-esp#34

May be it is a better way to answer the api call to not existing entities (like custom entities, analogue sensors, ...) with "INFO" and the answer "nothing configured for <api-call customs|sensor|analogue|...>" instead of errors.

just my idea - no problem today, as v2.4.1 has this configurable.

Thank You+++
Harvey

[proddy]

So the change here is that when you have no Custom Entities configured, a call to http:///api/custom/ should return an empty JSON {} and not log an Error with the message "unknown device".

[proddy]

did a PR with this change (3.6.2-dev-1). Now if there are no custom entities it'll come back with a message 'no entities'.