The logger configuration is dealt with in the docs.
Why you would not want to log an error is beyond me though.
Because I have the situation that the call should only clarify if a device is on or off. Off means āConnect call failedā. So best case I have the state on if on and off if not reachable. And in this case, this is not an error in my point of view in this case for me.
If I think wrong and you have a better idea for this usecase, Iām looking forward for some ideas.
I see what you are doing now. How about a ping sensor? https://www.home-assistant.io/integrations/ping/
Yes. But if āonā I want to have/request more attributes.
Same as more or less every other build in or custom integration. If a integrated device is not available, you have a special state (or the last state) but no error in the log. This is what I only want to achieve with the rest adapter as well. A kind of a customzisable error handler within the rest adapter instead of having the error in the log.
Thank you for that code, solves my problem!
Could you please fix the typo in āunavailableā? (You code says āunavialableā). I think this could help some people that find your code by searching for a solution, and it took me a while to see why it didnāt help first 
Fixed.
thanks for this. With this i can filter the problematic Aqara FP1 in my zigbee network which are going unavailable every few minutes.
pOpY