Screen settings and the next MQTT connection path

Observed work

Changing the Android industrial screen’s default launcher resolved the observed startup problem: a restart brought up the App and its data page. No APK change was needed for that issue. Point density and readability at the target resolution were then examined.

YenGear LoRa and Modbus diagrams were produced and revised with editable draw.io sources and SVG/PNG exports. Diagram guidance and export checks were added, and specification/manual synchronization started. Final agreement between the documents and exported files was not established.

A product application case was prepared as text and illustrations for the website and several social channels. laan reported that a greenhouse-case X post was public, but a public-page readback was not captured.

Document-repository checkout and synchronization procedures were organized. Some synchronization finished with warnings and bilingual documentation was committed locally. Evening SourceTree operations initiated further management-system and standalone-platform pushes, plus site-workflow and App threshold-interaction changes. Returning to a repository view without an error did not prove each remote update or deployment.

MQTT work introduced connection-parameter APIs and frontend v2 integration while reviewing the location of the shared messaging component and the split between cloud and standalone deployment. Reports covered 11 API tests, 337 main tests and a gateway push. The broker deployment script had not been deployed, and frontend integration and the complete path were still unverified.

QR-based project access was discussed with no App member-management feature in the current scope. That was a design decision rather than a completed production flow. External technical-community participation and operation of the owned community were also separated; publication results were not captured.

Screen settings were revised for viewport-dependent row heights and per-project time/project-code switches, with frontend/backend tests and builds reported passing. Saving point groups had timed out through per-point database operations. Batch validation/writing reportedly saved and read back 12 points and was committed locally; migration application, final production deployment and hardware rechecks remained unknown.

Standalone-platform 0.2.0 and tag release preparation began, without a final receipt for the morning version/push commands. An evening main push returned without a visible error, but remote tags/version were not independently read back. The shared messaging component and deployment boundary remained under discussion; full standalone delivery was not accepted.