zgyarmati

I've looked into this briefly. It seems that this only happen with the digispark port of the i2c-tiny-usb fimware. Digispark uses an USB bootloader [micronucleus](https://github.com/micronucleus/micronucleus), and I suppose (but I...

Oddly it turned out that with my Digispark (likely a clone, i don't even remember where i bought it) i can't reproduce the issue, neither with reboot nor with switching...

I flashed the 1.6 version of the Micronucleus bootloader FW from here: https://github.com/mariusgreuel/micronucleus/tree/v1.06/firmware/releases (the file "micronucleus-1.06.hex") and on the top of that I flashed the i2c-tiny-usb main.hex from this repo....

@BeetleX99, thx for sharing this observation! The hub has an external power supply, or host-powered?

Indeed, using udev is the canonical way to solve this kind of issues under Linux. If you run `udevadm monitor` (as root), while plugging in/unplugging the device, you will see...

> > while plugging in/unplugging the device > > That's not possible if working remotely. The device HAS TO HAVE a unique name so it can be identified. Like: `i2c-tiny-usb-pushbuttons-inputs`...

I vote for this, as it also affects me, and the patch works for me well

+1

This one also hit me, but from a different angle, on my footprint the script didn't report the overlap between the silkscreen and the pad, see here: https://github.com/KiCad/kicad-footprints/pull/1558#issuecomment-486897238 See this...

Indeed, http://www.grantlee.org is down. Is it still considered the official homepage of the project? (asking to know whether it's still can be used in downstream distros for package description)