From 4473d8117620dc8073f364414c455d6eeb7a294c Mon Sep 17 00:00:00 2001 From: Daniel Frenkel Date: Tue, 17 Nov 2026 07:10:36 -0800 Subject: [PATCH] firmware: valar-core v0.3.1 -- verified TLS for the GitHub update Bumps valar-core + scheduling from v0.2.0 to v0.3.1 on both boards. v0.3.1 = valar-motion #10: http_request verify_ssl on (the CMN CA bundle was already compiled in; +144 B), and a "Firmware Update" diagnostic that shows Downloading N% / Installed - restarting / Failed: . Firmware unchanged. Fixes valar-motion #9 for Ropener. v0.2.0 -> v0.3.0 only parameterized stepper constants with defaults equal to the old literals; the resolved stepper block is identical. Full resolved-config diff vs v2.12.1, both boards: only verify_ssl, the new entity + its Idle at boot, and the http_request OTA events (rest is logger.log key-order noise). Gate: +1 diagnostic entity, on_boot 600. Docs: user guide troubleshooting + quick reference, firmware README. Co-Authored-By: Claude Opus 5.5 --- docs/Ropener-User-Guide.md | 2 ++ firmware/README.md | 2 +- firmware/VAL3000/Ropener-VAL3000.yml | 4 ++-- firmware/VAL3100/Ropener-VAL3100.yml | 4 ++-- 4 files changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/Ropener-User-Guide.md b/docs/Ropener-User-Guide.md index 917ab29..833dfdc 100644 --- a/docs/Ropener-User-Guide.md +++ b/docs/Ropener-User-Guide.md @@ -336,6 +336,7 @@ Every other reading and setting on the web page has its own topic under the same | No setup hotspot appears | Wait a full minute after power-on. If it already joined a network, hold Button 3 for 3–10 seconds to reset Wi-Fi and try again. | | Open/Close are reversed | Set the “Motor Direction” setting to **Reversed**. | | Position is wrong / drifted | Run homing (Section 5) to recalibrate. | +| “Update Firmware (GitHub)” didn't update | Check **Firmware Update** under Diagnostics: it shows the progress or why the update failed (for example no internet, or GitHub's security certificate couldn't be verified). A failed update never changes the firmware the device is running — fix the cause and press the button again. | | Curtain closes a little shorter every cycle | First check **Driver Temperature** and **Driver Shutdowns** under Diagnostics. If Driver Temperature ever shows Hot or Overheated, or Driver Shutdowns is above 0, the motor driver is cutting out on long runs: **lower** the Motor Current (IRUN) and keep Speed at Medium. Otherwise the rope may be slipping. In either case, Close Overtravel (Section 10) makes up the difference on every close. | | Schedule fires at the wrong time | Check the Timezone value (Section 7/8) and that the device has internet for time sync. | | Schedule doesn't run | Confirm “Schedule Enabled” is ON and that Open/Close times are set. | @@ -371,6 +372,7 @@ Every other reading and setting on the web page has its own topic under the same | SG_RESULT / TSTEP | Live readings used when tuning homing. | | Driver Temperature | Motor driver health: OK, Hot, Overheated, or “Overheated earlier – re-home” (Diagnostics). | | Driver Shutdowns | How many times the motor driver has shut off since the last restart (Diagnostics). Each one loses position. | +| Firmware Update | Progress of the last “Update Firmware (GitHub)” press, or why it failed (Diagnostics). | | MQTT Broker / Port / Username / Password / Enabled | Connect to an MQTT broker (Section 11). | | MQTT Status | Off, Connecting…, Connected with the topic prefix, or “press Restart to Apply” after a change. | | Restart to Apply | Restarts the device so changed MQTT settings take effect. | diff --git a/firmware/README.md b/firmware/README.md index e4a56f1..440be9a 100644 --- a/firmware/README.md +++ b/firmware/README.md @@ -50,5 +50,5 @@ Hold-to-run is the child- and elderly-friendly mode: the curtain only moves whil Two ways to update: -- **Over the air, from the device:** open the settings page and, under Diagnostics, press **"Update Firmware (GitHub)"**. The device downloads the latest release for its model straight from GitHub, flashes itself, and reboots — no computer needed. (Requires an internet connection.) +- **Over the air, from the device:** open the settings page and, under Diagnostics, press **"Update Firmware (GitHub)"**. The device downloads the latest release for its model straight from GitHub, flashes itself, and reboots — no computer needed. (Requires an internet connection.) **Firmware Update** (also under Diagnostics) shows the progress, or why an update failed; a failed update leaves the current firmware running. - **Manually:** download the `*.ota.bin` (for a device already on your network) or `*.factory.bin` (for a fresh USB flash) for your model from the [latest release](https://github.com/Valar-Systems/Ropener/releases/latest) and upload it as before. diff --git a/firmware/VAL3000/Ropener-VAL3000.yml b/firmware/VAL3000/Ropener-VAL3000.yml index 873473b..ce2c7c6 100644 --- a/firmware/VAL3000/Ropener-VAL3000.yml +++ b/firmware/VAL3000/Ropener-VAL3000.yml @@ -32,12 +32,12 @@ esphome: packages: valar_core: url: https://github.com/Valar-Systems/valar-motion - ref: v0.2.0 + ref: v0.3.1 files: [common/valar-core.yaml] refresh: 1d scheduling: url: https://github.com/Valar-Systems/valar-motion - ref: v0.2.0 + ref: v0.3.1 files: [common/scheduling.yaml] refresh: 1d product: !include ../common/ropener-product.yaml diff --git a/firmware/VAL3100/Ropener-VAL3100.yml b/firmware/VAL3100/Ropener-VAL3100.yml index d8403af..a539708 100644 --- a/firmware/VAL3100/Ropener-VAL3100.yml +++ b/firmware/VAL3100/Ropener-VAL3100.yml @@ -33,12 +33,12 @@ esphome: packages: valar_core: url: https://github.com/Valar-Systems/valar-motion - ref: v0.2.0 + ref: v0.3.1 files: [common/valar-core.yaml] refresh: 1d scheduling: url: https://github.com/Valar-Systems/valar-motion - ref: v0.2.0 + ref: v0.3.1 files: [common/scheduling.yaml] refresh: 1d product: !include ../common/ropener-product.yaml