Live telemetry and application submission reports

Observed work

The shared serial I/O manual again covered Y301-220, Y301-222, Y301-440, Y301-444 and Y301-880. Names and references were normalized rather than copying shared material into separate model manuals. Checks and local commits were reported. The catalog put module categories before finished field equipment; the later main-branch push was not independently confirmed.

DataLogger environment selection and Django-management responsibilities were clarified, with configuration folders and entry names revised. Cloudflare traffic allocation and D1 health checks passed according to reports; anonymous requests were rejected as intended. Authenticated and critical business APIs still needed inspection.

New Cloudflare image writes moved toward R2, retaining read-only access to old images. Regression and deployment reports were followed by a decision to reuse an existing bucket. Complete online checks of uploading, replacement, deletion and legacy protection were not captured.

Fixing the mini-program base-library configuration produced a successful 2.1.0 upload receipt. Review and public release remained later steps. Version configuration and personal/About displays were then centralized: mini-program 2.1.5, App and H5 2.1.0. Tests, package checks and a local commit were reported. The later 2.1.5 upload lacked a success or failure receipt.

Chinese and English cloud-App landing pages used H5 screenshots when the simulator was unavailable. Reports subsequently covered merge, push, deployment and public access, and both sitemaps were resubmitted. A separate English-page indexing request ran into a connection failure; its retry outcome was unknown.

YenGear Cloud was chosen as the English App name and some local branding material was aligned. Published packages and other online assets still needed their own updates. Android distribution shifted to local compilation and manual publication without a captured package or release. Local certificate/release-material cleanup was requested, with no final result.

Rebuilding and clearing caches enabled mini-program login, device/temperature views and continuous live data, although developer warnings/errors remained. Local fixes to privacy-page messaging recovery and overlapping threshold labels were reportedly committed but unpushed. Receiving data did not settle command execution, state readback or full offline recovery.

After build delivery and Apple processing, icon and permission-text changes were followed by a report that 2.1.0 (20103) uploaded and entered waiting-for-review state. I did not independently inspect the store backend, and approval/public listing was not yet established. Apple-login backend/test-server checks were reported, without real iPhone authorization.