Version 4.0.0

Breaking Changes

• The new minimum ESPHome version is 2024.6.0 due to changes made to OTA components

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 3.0.0

⚠️ BREAKING CHANGES — READ THIS BEFORE UPDATING! ⚠️

This version contains two major, breaking changes:

• The Bluetooth Proxy component has been removed from the stock firmware due to performance issues reported by several users. You can re-add the component if you wish: More Info
• The firmware is now compiled using the ESP-IDF framework instead of Arduino. This should offer better performance (especially if you re-enable the Bluetooth Proxy component) but has some implications for flashing. Read below to understand them and avoid bricking your Upsy Desky.

Please report any issues you experience with this new version.

Flashing Instructions

Due to the switch from Arduino to ESP-IDF, the partition structure of the binaries are different. This means you CANNOT cleanly OTA this firmware over any other previous version; you MUST flash via USB.

If you are using ESPHome Dashboard, physically plug the device into your computer and flash the new firmware using the web UI.

If you are not using ESPHome Dashboard (i.e., totally stock firmware), you must install the firmware via USB. Note that this will factory reset your Upsy Desky and you will need to go through the setup process again. More info is available here

Version 2.0.0

Breaking Changes

The new minimum version of ESPHome is 2023.12. This is due to a change with ESPHome which now requires an explicit declaration that a pin can be used in multiple places. This change is backwards incompatible with other ESPHome versions; it will not recognize the option and fail. More details here: #41

If you are still on a version of ESPHome earlier than 2023.12, you can target the branch pre-esphome-2023.12, but please note that it will not receive updates.

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.2.0

Breaking Changes

If you base your ESPHome config off the stock firmware (stock.yaml), note that the Bluetooth proxy component will no longer proxy active connections. This was changed to improve performance and prevent OOM. It does not affect passive connections; see the note on active connections at the ESPHome docs.

If you wish to re-enable this behavior, add this to your config:

substitutions:
  bluetooth_proxy_active_connections: "true"

If you are using the bluetooth-proxy addon package standalone, you are not affected.

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.1.2

Breaking Changes

The bluetooth-proxy addon is no longer included by default in the base config (base.yaml) and is instead included only in the stock firmware config (stock.yaml). If you use the base config in your ESPHome configuration and still wish to retain the Bluetooth proxy, you can add it yourself by adding these lines to your config:

esp32_ble_tracker:

bluetooth_proxy:
  active: false # Change to true if you wish to proxy active connections as well (warning: comes with performance impact)

New Features

This firmware release adds support for Improv over BLE to the stock firmware, which makes setup much easier for those with a Bluetooth-enabled Home Assistant instance. Here is an example of the process from the Home Assistant blog:

cropped.mp4

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.1.1

This is basically just a re-release of 1.1.0 because I forgot to add this line to the config. Oops!

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.1.0

• (#33) Display current version number on web interface and link to instructions on updating

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

v1.0.4

• Remove the deprecated api.password field from the stock firmware YAML

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.0.3

• Bring back runtime height units config with support for ESPHome 2023.5 (related: #32)

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.

Version 1.0.2

• Temporarily remove "Height Units" runtime configuration option due to an incompatibility with ESPHome 2023.5
  • You can customize the height units by adding this to your configuration YAML under substitutions:

    standing_desk_height_units: "cm"

Flashing

See the documentation for more information on how to non-destructively update the firmware via an OTA.

If you are flashing an OTA to your Upsy Desky, use the firmware.bin asset. If you are flashing from scratch, use firmware-factory.bin instead.