Adam van Gaalen

Hi xypron, No way to trigger it... I just wrote and ran a script to check the logfiles every 10 minutes or so. I did find out, that one of the sispm's serial-number appeared to be incremented a couple of times every hour... I took the USB-cable of that sispm away from the hub that is was connected to and plugged it into a free port on the Pi. That seems to have solved the problem (fingers crossed now). When unplugging I noticed that the plug was kind of loosely connected to the hub-port that it had...

I noticed, in the output above, that the devices were not 'nicely' numbered... I did a reboot and now the output looks like: Bus 001 Device 010: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 009: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 007: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 006: ID 04b4:fd13 Cypress Semiconductor...

Oops, I missed your posting, sorry for that. lsusb now says: 8:46 mainsberrypi: Command? lsusb Bus 001 Device 010: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 053: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 017: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 006: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket...

I keep getting: usb 1-1.5.3: usbfs: USBDEVFS_CONTROL failed cmd sispmctl