Release 2.8.1

⚠️⚠️⚠️
To install and run owlcms-firmata, you need to use the OWLCMS Control Panel. This location now only the release notes and the software modules that the control panel will install for you.

• The OWLCMS Control Panel can be downloaded at this location. and you can refer to the Installation Instructions
• User Documentation for the Control Panel is located at this location

Release Notes

• 2.8.1: Fixed the tone generation for the "summon all" case.

• 2.8.0

  • Jury boxes (BlueOwl-Jury and JuryFull configurations): the referee lights now turn green when owlcms reports a referee decision as hidden (fop/decision N hidden), the same as the jury member lights. This is used by the four-member jury review vote in owlcms 69 (TCRR October 2026).
  • Multiple Firmata instances can connect to the same owlcms server without repeatedly disconnecting one another's configuration connection, including when an instance has no devices detected.
  • Fix for missing jar that prevented 2.7.0 from starting

• 2.7.0

  • Summon all referees: the referee buzzers now sound together as a single tone that lasts as long as when a single referee is summoned. Previously the sound was distorted and much longer.
  • macOS: device detection only probes usable serial ports, so boards are no longer listed twice and detection no longer waits on Bluetooth and debug ports.
  • If the configuration folder contains no device configurations, they are copied again from the distribution.
  • Technical: migrated to Vaadin 25 and Java 25. The Control Panel installs the required Java automatically.

• 2.6.1

  • No changes in features or behavior. This version fixes the missing release notes and the build process

• 2.6.0:

  • This version is installed from the Control Panel version 3.0.4 or more recent
  • There is no longer a separate firmata control panel

• 2.5.1: Connections when username/password were configured on owlcms no longer worked in 2.5.0

  • A wrong password will now interrupt the initial autoconnect correctly and give an opportunity to fix the password
  • Fixes were applied to both the MQTT protocol (port 1883) and websocket connections as the Paho library reports errors in different ways.

• 2.5.0: Support for websockets

  • If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. For example, testingMqtt.fly.dev with port 443 will connect to wss://testingMqtt.fly.dev:443/mqtt
  • If the port starts with 8 the connection will be using ws: instead of wss:. For local tests you can use localhost with port 8080 (or the normal HTTP port of OWLCMS you use). OWLCMS will be called on the detected machine as ws://{detected}:8080/mqtt.
  • Otherwise, mqtt is used (the normal 1883 uses the mqtt protocol)

Release 2.8.0

⚠️⚠️⚠️
To install and run owlcms-firmata, you need to use the OWLCMS Control Panel. This location now only the release notes and the software modules that the control panel will install for you.

• The OWLCMS Control Panel can be downloaded at this location. and you can refer to the Installation Instructions
• User Documentation for the Control Panel is located at this location

Release Notes

• 2.8.0

  • Jury boxes (BlueOwl-Jury and JuryFull configurations): the referee lights now turn green when owlcms reports a referee decision as hidden (fop/decision N hidden), the same as the jury member lights. This is used by the four-member jury review vote in owlcms 69 (TCRR October 2026).
  • Multiple Firmata instances can connect to the same owlcms server without repeatedly disconnecting one another's configuration connection, including when an instance has no devices detected.
  • Fix for missing jar that prevented 2.7.0 from starting

• 2.7.0

  • Summon all referees: the referee buzzers now sound together as a single tone that lasts as long as when a single referee is summoned. Previously the sound was distorted and much longer.
  • macOS: device detection only probes usable serial ports, so boards are no longer listed twice and detection no longer waits on Bluetooth and debug ports.
  • If the configuration folder contains no device configurations, they are copied again from the distribution.
  • Technical: migrated to Vaadin 25 and Java 25. The Control Panel installs the required Java automatically.

• 2.6.1

  • No changes in features or behavior. This version fixes the missing release notes and the build process

• 2.6.0:

  • This version is installed from the Control Panel version 3.0.4 or more recent
  • There is no longer a separate firmata control panel

• 2.5.1: Connections when username/password were configured on owlcms no longer worked in 2.5.0

  • A wrong password will now interrupt the initial autoconnect correctly and give an opportunity to fix the password
  • Fixes were applied to both the MQTT protocol (port 1883) and websocket connections as the Paho library reports errors in different ways.

• 2.5.0: Support for websockets

  • If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. For example, testingMqtt.fly.dev with port 443 will connect to wss://testingMqtt.fly.dev:443/mqtt
  • If the port starts with 8 the connection will be using ws: instead of wss:. For local tests you can use localhost with port 8080 (or the normal HTTP port of OWLCMS you use). OWLCMS will be called on the detected machine as ws://{detected}:8080/mqtt.
  • Otherwise, mqtt is used (the normal 1883 uses the mqtt protocol)

Release 2.7.0

⚠️⚠️⚠️
To install and run owlcms-firmata, you need to use the OWLCMS Control Panel. This location now only the release notes and the software modules that the control panel will install for you.

• The OWLCMS Control Panel can be downloaded at this location. and you can refer to the Installation Instructions
• User Documentation for the Control Panel is located at this location

Release Notes

• 2.7.0

  • Summon all referees: the referee buzzers now sound together as a single tone that lasts as long as when a single referee is summoned. Previously the sound was distorted and much longer.
  • macOS: device detection only probes usable serial ports, so boards are no longer listed twice and detection no longer waits on Bluetooth and debug ports.
  • If the configuration folder contains no device configurations, they are copied again from the distribution.
  • Technical: migrated to Vaadin 25 and Java 25. The Control Panel installs the required Java automatically.

• 2.6.1

  • No changes in features or behavior. This version fixes the missing release notes and the build process

• 2.6.0:

  • This version is installed from the Control Panel version 3.0.4 or more recent
  • There is no longer a separate firmata control panel

• 2.5.1: Connections when username/password were configured on owlcms no longer worked in 2.5.0

  • A wrong password will now interrupt the initial autoconnect correctly and give an opportunity to fix the password
  • Fixes were applied to both the MQTT protocol (port 1883) and websocket connections as the Paho library reports errors in different ways.

• 2.5.0: Support for websockets

  • If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. For example, testingMqtt.fly.dev with port 443 will connect to wss://testingMqtt.fly.dev:443/mqtt
  • If the port starts with 8 the connection will be using ws: instead of wss:. For local tests you can use localhost with port 8080 (or the normal HTTP port of OWLCMS you use). OWLCMS will be called on the detected machine as ws://{detected}:8080/mqtt.
  • Otherwise, mqtt is used (the normal 1883 uses the mqtt protocol)

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

Release 2.6.1

⚠️⚠️⚠️
To install and run owlcms-firmata, you need to use the OWLCMS Control Panel. This location now only the release notes and the software modules that the control panel will install for you.

• The OWLCMS Control Panel can be downloaded at this location. and you can refer to the Installation Instructions
• User Documentation for the Control Panel is located at this location

Release Notes

• 2.6.1

  • No changes in features or behavior. This version fixes the missing release notes and the build process

• 2.6.0:

  • This version is installed from the Control Panel version 3.0.4 or more recent
  • There is no longer a separate firmata control panel

• 2.5.1: Connections when username/password were configured on owlcms no longer worked in 2.5.0

  • A wrong password will now interrupt the initial autoconnect correctly and give an opportunity to fix the password
  • Fixes were applied to both the MQTT protocol (port 1883) and websocket connections as the Paho library reports errors in different ways.

• 2.5.0: Support for websockets

  • If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. For example, testingMqtt.fly.dev with port 443 will connect to wss://testingMqtt.fly.dev:443/mqtt
  • If the port starts with 8 the connection will be using ws: instead of wss:. For local tests you can use localhost with port 8080 (or the normal HTTP port of OWLCMS you use). OWLCMS will be called on the detected machine as ws://{detected}:8080/mqtt.
  • Otherwise, mqtt is used (the normal 1883 uses the mqtt protocol)

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

Release 2.6.0-rc03

startup.log

Release 2.6.0-rc02

create tag

Release 2.6.0

2.6.0

owlcms-firmata 2.5.1

In this release

• 2.5.1: Connections when username/password were configured on owlcms no longer worked in 2.5.0

  • A wrong password will now interrupt the initial autoconnect correctly and give an opportunity to fix the password
  • Fixes were applied to both the MQTT protocol (port 1883) and websocket connections as the Paho library reports errors in different ways.

• 2.5.0: If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. If the port starts with 8 the connection will be using ws:. Other ports, like the usual 1883 will use mqtt

Since 2.3.0

• 2.4.0: Removed unneeded connections established at start-up. This version should be used for clarity when using owlcms version 61 Connected MQTT devices status reporting.
• 2.3.3: Show the full path to the device definition files.
• 2.3.2: Fix subscription issues when Disconnecting and reconnecting to a server with different platform names
• 2.3.1: Reset the platform list when doing a Disconnect/Connect
• 2.3.0: Automatic connections
  • on startup, automatic connection attempted to the last working configuration
  • if that does not work, scan of the local area network to locate an MQTT server
  • manual choice remains possible
  • once a platform is selected, automatic connection to the detected devices

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.5.0

In this release

• 2.5.0: If the port specified ends with 443, the connection will be done using wss: to the /mqtt entry point. This is to support the use of MQTT devices on a cloud server. If the port starts with 8 the connection will be using ws:. Other ports, like the usual 1883 will use mqtt

Since 2.0

• 2.4.0: Removed unneeded connections established at start-up. This version should be used for clarity when using owlcms version 61 Connected MQTT devices status reporting.
• 2.3.3: Show the full path to the device definition files.
• 2.3.2: Fix subscription issues when Disconnecting and reconnecting to a server with different platform names
• 2.3.1: Reset the platform list when doing a Disconnect/Connect
• 2.3.0: Automatic connections
  • on startup, automatic connection attempted to the last working configuration
  • if that does not work, scan of the local area network to locate an MQTT server
  • manual choice remains possible
  • once a platform is selected, automatic connection to the detected devices
• 2.2.0: Fix: pin outputs with "ON" but no duration were not working. (These are needed for full jury panel)
• 2.1.1: Do not overwrite files on startup, to work with firmata-controlpanel 0.9.1 simplified updating methods.
• 2.1.0: fix to work with version 55.3
• 2.0.8: work with a control panel similar to that of owlcms
  • the control panel will pass additional options to tell where the configuration files are and what port to use.
• 2.0.6: fixed the configuration selection to work on Linux and Raspberry Pi.
• 2.0.5: clientId now less than 23 characters to prevent spurious error message in owlcms
• host/port/username from last connection are saved and restored on next start
• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.4.0

In this release

• 2.4.0: Removed unneeded connections established at start-up. This version should be used for clarity when using owlcms version 61 Connected MQTT devices status reporting.

Since 2.0

• 2.3.3: Show the full path to the device definition files.
• 2.3.2: Fix subscription issues when Disconnecting and reconnecting to a server with different platform names
• 2.3.1: Reset the platform list when doing a Disconnect/Connect
• 2.3.0: Automatic connections
  • on startup, automatic connection attempted to the last working configuration
  • if that does not work, scan of the local area network to locate an MQTT server
  • manual choice remains possible
  • once a platform is selected, automatic connection to the detected devices
• 2.2.0: Fix: pin outputs with "ON" but no duration were not working. (These are needed for full jury panel)
• 2.1.1: Do not overwrite files on startup, to work with firmata-controlpanel 0.9.1 simplified updating methods.
• 2.1.0: fix to work with version 55.3
• 2.0.8: work with a control panel similar to that of owlcms
  • the control panel will pass additional options to tell where the configuration files are and what port to use.
• 2.0.6: fixed the configuration selection to work on Linux and Raspberry Pi.
• 2.0.5: clientId now less than 23 characters to prevent spurious error message in owlcms
• host/port/username from last connection are saved and restored on next start
• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.