v3.2.0

What's Changed

• This module now requires Companion ≥3.4.0.
• The TCP connection this module creates to interact with a camera is more resiliently managed.
  • If the attempt to connect fails, or if the connection fails or is closed by the camera, the module will automatically try to reconnect until a connection is established. Any VISCA commands sent to the camera that are currently being processed will not be reattempted, because performing a command twice might not have the same effect as performing it once. (For example, a command instructing the camera to rotate by 25° would rotate 50° if performed twice.)
  • Camera responses that violate VISCA requirements will cause the connection to fail. No attempt is made to reconnect in this case. Whatever conditions triggered the violation might be present on reconnection (triggering an infinite error loop), so cleaning up and manually restarting the instance is left to the user (e.g. using a trigger that watches the instance status).
  • Instance status is consistently synced with the state of the TCP connection.

Manual install instructions

In Companion 3.4 or later:

1. Create an empty folder somewhere and give it a name like companion-dev-modules.
2. In that folder, extract the companion-module-ptzoptics-visca.tgz — such that companion-dev-modules/pkg/companion/manifest.json will exist.
   • You can rename the extracted pkg folder to another name if needed.
3. In Companion's launch window, click the little gear icon in top right, and set the "Developer modules path" at bottom to the companion-modules-dev folder.

You can verify that the module installed correctly using the "Help" icon on any connection's configuration page.

Full Changelog: v3.1.0...v3.2.0