{"id":1787,"date":"2023-06-07T16:22:53","date_gmt":"2023-06-07T20:22:53","guid":{"rendered":"https:\/\/techministry.blog\/?p=1787"},"modified":"2023-06-07T16:22:53","modified_gmt":"2023-06-07T20:22:53","slug":"notify-production-team-members-remotely-using-open-source-software-and-low-cost-usb-busy-lights","status":"publish","type":"post","link":"https:\/\/techministry.blog\/?p=1787","title":{"rendered":"Notify production team members remotely using open source software and low cost USB busy lights"},"content":{"rendered":"\n

At my church, we have a couple of these:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

They’re great. Expensive, but they work well.<\/p>\n\n\n\n

The problem for us is that anytime anyone presses the Call light on the intercom party line, any flashers on that party line will light up. This means we can really only have 1 unique flasher per line.<\/p>\n\n\n\n

Sometimes, we want or need to get a specific person\/position’s attention.<\/p>\n\n\n\n

I created some software to help with this. It’s called beacon<\/strong>.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

It’s a small app that runs in the system tray and hosts a network API so you can signal a USB busy light, such as the Luxafor Flag or Thingm blink(1). Or, if you don’t have or want a physical signal light, you can also have an on-screen dot that you can use.<\/p>\n\n\n\n

\n