@heizelmann I am currently investigating this further. Among other things I have created a fork of the cap package which replaces the status assertion with an output of the status. If you have some time to do also some testing you can
npm install mwittig/pimatic-amazing-dash-button.
Expected behaviour: Pimatic should no longer hang or abort. The log file may contain some messages containing “Error: Libuv status code”. If you see this, please let me know about the status code(s) you get. Besides this I do not expect the operation of the plugin or the rest of pimatic is impacted by the error. However, it needs to check if the error is just temporary and the plugin still detects button push events or capturing runs into permanent failure.
I am also trying to create an isolated test case for the development, but for this I need more information about the nature of the error.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law