be friendly to possibly correct requests

[harvey637]

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://<hostname>/api/custom/ should return an empty JSON {} and not log an Error with the message "unknown device".

[harvey637]

Hi Proddy,Yes, petfect solution.Have a good Weekend!Ciao Harvey--Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.Am 17.09.23, 09:46 schrieb Proddy ***@***.***>: So the change here is that when you have no Custom Entities configured, a call to http://<hostname>/api/custom/ should return an empty JSON {} and not log an Error with the message "unknown device". —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>