Backend release and product follow-up

Observed work

The corrected backend release reportedly brought the server and cloud functions onto one version after nine migrations and an unavailable image-layer dependency. Startup, Django, queues and scheduling checks passed according to the report, while complete image-processing coverage and the separate gateway build remained open. Quota editing also had a production-release report. Later status said the two custom plans were gone and their subscriptions had moved to the basic plan. An advisor scheduling investigation found repeated dependency timeouts and no configured advisors or run records; the production schedule was reported disabled, with deployment settings changed to preserve that pause.

A real import API exercised against an isolated database distinguished Modbus types at the same address. Y301-110, Y301-220, Y301-440 and Y301-880 templates were then corrected for an offset caused by incrementing both address and data index. Reports covered production-template readback, offline message checks, backup and an operation log. The templates affect future imports, not existing device points automatically. Real device traffic and the complete historical-ID migration were not accepted.

TradeTool query prices were rounded upward while detailed precision was retained. Tests and a main-branch push were reported, without a deployment readback for that change. Local Worker access still failed after a redirect repair, and later copying had no confirmed outcome. The inquiry admin had a separate empty-timestamp read error: its repair passed checks and was pushed, then a follow-up report described the deployment and production verification as complete. That report does not establish acceptance of every historical record or business path.

Account traffic notifications added optional SMS recipients, separate channel state and per-account limits. Some tests, server deployment and configuration pushes completed according to reports. Requested redeployment and real SMS receipt were still unknown. Internal notification boundaries/recipient settings were refined; production variables encountered a maintenance-version block. A separate cloud budget task lost its schedule while retaining state storage, which did not validate all protection mechanisms.

Some zero-weight store variants were filled from documentation and read back, with other models still needing sources. Local documentation changes did not establish store synchronization. The serial-gateway selector gained gateway attributes and cellular-region choices; laan exercised filters and requested a tagged release, without complete production storefront verification. Overlapping bands were not treated as a carrier-compatibility guarantee.

Y401WG-L auxiliary interfaces/pairing and compatibility with Y301-220 were investigated, with bilingual specification changes based on laan’s additions. Output electrical type, multichannel behavior and interface compatibility still needed manufacturer confirmation. Five alarm product pages received image/layout revisions with passing build/format checks but incomplete browser and release acceptance. Battery/solar estimates depended on capacity, current and sunlight assumptions, without measured runtime.

Settlement wording and business worksheets were revised, and a pro forma invoice PDF export had visible success. Sending, settlement and payment were not established. Remote access still failed.

The landing-form repair kept the API route, fixed runtime request parameters and passed focused tests before a reported push. A production test submission/notification and replay of old failed notifications were reported successful. Those included test/invalid entries, so replay counts were not qualified leads. Whether engagement events should require ad parameters remained under discussion without a captured change.

An industrial wireless-alert inquiry advanced through signal/group clarification, technical documents and a quotation, with a question about a pro forma invoice. Independent-group isolation and communication behavior were still unverified. Requirement agreement was not tested compatibility, and there was no completed invoice, order, payment or delivery.