Julian Waller

[RFC] Instance status

3

### Describe the feature Instances have two methods they can use to report status/information back to the user https://github.com/bitfocus/companion/blob/df1ca54d523547faebe4377a80837bf97026d552/instance_skel.d.ts#L158-L160 `log` will append lines only visible in the log tab `status`...

Expose properties instead of actions

4

**Describe the feature** I have been thinking about this for a while, as exposing numeric properties in device modules gets really repetitive, especially when wanting to allow actions to do...

### Is this a feature relevant to companion itself, and not a module? - [X] I believe this to be a feature for companion, not a module ### Is there...

feat: HIDAsync

2

This continues on from the discussions in #451. Im doing this as a separate PR as the changes to the HID class have been reverted. The intention is that this...

feat: run async read on std::thread instead of uv threadpool

16

This resolves the issue with not being able to read from more than 4 devices simultaneously unless `UV_THREADPOOL_SIZE` is increased. https://github.com/node-hid/node-hid/issues/408 Instead of using the uv-pool to run the reads,...

Any chance of prebuilds for linux-arm64 being added? Im curious, how are you producing these prebuilds currently? Anything I could help automate via some github actions scripting? Perhaps something from...

Add hid_get_device_info

23

Resolves: #431 Closes: #164 Closes: #163 I don't like the signature of `get_device_info_for_device` in linux, and Im unsure about `fill_device_info_for_device` in libusb. The mac, linux and libusb implementations appear to...

Get vendorId & productId from hid_device or path

1

I maintain a couple of nodejs libraries (such as [elgato-stream-deck](https://github.com/Julusian/node-elgato-stream-deck)) which use this library via [node-hid](https://github.com/node-hid/node-hid). In those I expose a method which takes in a path to the device...

Connection reset by peer

5

- [x] I have read the [README.md](https://github.com/flyte/pi-mqtt-gpio/blob/develop/README.md) file and visited the [Documentation](https://mqtt-io.app/) to see if the information there helps. **Describe the bug** Not reconnecting to MQTT **Expected behavior** The software...

feat: Timecode & scheduler

9

#871 #872 #1004 This adds support for timecode input and output via decklinks, and for being able to schedule commands to be executed at various timecodes. It also adds a...