Mini-program checks and iOS release preparation

Observed work

A disabled schedule was created in the mini-program while device data and linkage forms were inspected. Automation repairs were reported committed and pushed with 36 tests and mini-program/App builds passing. One linkage rule remained in the form without a confirmed save; automatic execution was not verified.

Project membership and QR entry were specified more precisely: removing a member removes that project’s access; invitations default to read-only and expire; cross-project roles limit permission editing. Some member and QR pages displayed, while other tests encountered placeholders, API errors and timeouts. Full acceptance was still outstanding.

Configuration-tool model and device labels were reviewed with underlying read/write values kept unchanged. Some models remained missing from the display mapping. A USB-to-RS485 adapter could reportedly be opened, but wiring, protocol response and real-device communication were not established; a simulated save notice was insufficient.

DataLogger deployment files, environment templates and tests were reorganized around choosing an environment before an operation. Incremental migrations and rebuilding were separated, with rebuilding limited to local and Cloudflare testing while preserving production and Vercel behavior. Local checks passed; a cloud migration preview met a concurrent-write guard and no cloud write was recorded. Some command semantics remained undecided.

YenGear Toolbox download and updater configuration, tests and instructions were revised. Rebuilding was still running; the online update manifest returned 404 and the first package had not been uploaded. The update service was therefore not yet verified usable.

LoRa blog illustrations, homepage material, API information and documentation cleanup were reviewed. A product-document commit was initiated. Some checks passed, but page/test problems and uncaptured commit, push and publication outcomes remained.

Mini-program logs briefly showed a successful connection/subscription and some device/rule pages opened. A later test repeatedly received 503 from the connection API. This did not establish stable reconnect or complete device execution/state readback.

UMS 2.1.0 iOS preparation began with a passing App-resource build and selection of store naming, signing, icon and screenshot material. Cloud packaging reached resource compilation/checking. Issued/downloaded certificates, a valid signed IPA, Transporter upload and review submission were not captured; icon/screenshot acceptance was also unfinished.