Degraded UX when attempting to interact with non-coap hosts
Teufelchen1 opened this issue · 1 comments
Teufelchen1 commented
Hello 🐦
When running aiocoap-client coap://[valid_v6%interface]/
against a device that is up and reachable but does not run a coap server, the user get the awful error: Network error: [Errno 111] received through errqueue
. While one can look up the errno number, this is still unnecessary hard and imho a UX failure.
Expected behaviour:
The host is up but refuses packets on the coap default port. Are you sure there is a coap server running? Is it on a non default port? (Network error: [Errno 111] received through errqueue)