search for: interrupt_read

...ons... none (-110) upsdrv_updateinfo... Waiting for notifications... none (-110) upsdrv_updateinfo... (and so on and on) Checking out the code (2.2.0) I notice that the interrupt read function that is called just prior to the "none" message is basically just a stub, i.e. int shut_interrupt_read(shut_dev_handle_t *dev, int ep, unsigned char *bytes, int size, int timeout) { /* sleep during timeout to slow down a bit... */ sleep(timeout / 1000); /* FIXME: to be written */ return 0; } However, it automatically returns a zero, i.e....