mark-epstein
commented
3 years ago I had a very similar issue again yesterday. I know yesterday's incident stemmed from a USB hub being powered off (because it was the easiest way to reset a Stream Deck) and I suspect the event 2 weeks ago might have been the same.
I'm going to close this issue and create a related enhancement request
I've worked tech support enough to know where this is probably headed but it's worth a shot...
I had Companion (v2.1.2) running on my RPi for probably weeks, and probably a week since the last RPi reboot, and everything was going great. Yesterday in the middle of a church service, my buttons that send MIDI to a USB MIDI port just stopped doing so. Being the middle of the service there wasn't a whole lot I could do, but I do think I verified that Companion's log didn't indicate any errors, and
pm2 logs midi-relaysuggested that the software was successfully sending. But ultimately I couldn't control my lights.The next device in the path converts MIDI notes to DMX lighting cues, but it has minimal diagnostics and rebooting it would have caused a jarring loss of all lights, so we carried on through the entire service with all the lights at 100%.
Post-service I rebooted the DMX box (but got no improvement. Finally I rebooted the RPi and everything was back to normal. Yes I could have done that earlier but I didn't expect it to help, and I was afraid of what else might break.
Are there any post-mortem diagnostic steps that might help me understand what went wrong?
I'm currently (since yesterday afternoon, after the failure mentioned above) running Companion 2.2.0 because I needed the generic-tcp-serial module to control one of my cameras. I don't imagine this helps my chance of a solution, but hoping it doesn't hurt.