Make your standing desk smarter
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: https://github.com/tjhorner/upsy-desky/issues/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.
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.
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.
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.
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)
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:
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.
This is basically just a re-release of 1.1.0 because I forgot to add this line to the config. Oops!
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.
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.
api.password field from the stock firmware YAMLSee 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.
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.
substitutions:
standing_desk_height_units: "cm"
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.
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.
This version includes a major UX milestone: users no longer need to select the decoder to use manually! This was a very big source of friction (possibly the largest) since it was so confusing and opaque. Many requests for support I received were solved by simply choosing a different decoder. This eliminates the possibility of choosing the wrong one, and makes first setup much easier.
This is also a very big change internally. Existing configurations should not be affected (if variant is set manually in the YAML config, it will remain set), but if you run into any issues please let me know.
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.