Liquid Glass Weather

Help me install and verify Liquid Glass Weather on my computer.
Project repository: https://github.com/itopinion/zectrix-weather-glass
Installation guide: https://github.com/itopinion/zectrix-weather-glass/blob/main/README.md
Site review date: 2026-10-17; reference commit: 8313b20c5ba3adb22aacf49ca51f0aa0bde01d45. Recheck the current version before execution.
Project requirements: Python 3.10+ · WeatherAPI Key · Device-push integration required
Distribution status: Image generation · Push integration pending
The app source is public. Hub has not been officially released; its repository and bundled device SDK remain private.
Common device SDK source: https://github.com/itopinion/zectrix-hub/tree/main/crates/zectrix-cards/vendor/sdk (currently in a private repository; access required).
Cross-platform guide: https://github.com/itopinion/zectrix-hub/blob/main/docs/PORTING.md. Check compatibility between the current SDK and device firmware; do not blindly use versions from old documentation.
Identify the operating system, processor architecture and build toolchain first. Build from project source and the matching SDK for this system; do not download or distribute prebuilt Mac app packages. Create an isolated runtime for Python projects on the target system.

This version starts with local image generation. For device push, proceed to the Hub checks below. The repository has no device-push integration; do not report image generation as successful device display.
1. Check whether ZECTRIX Hub (https://github.com/itopinion/zectrix-hub) is already installed, including its running status, version and app interfaces. Reuse a compatible installation; do not reinstall, overwrite existing apps, settings or data, or open a competing device connection.
2. If Hub is missing, first confirm access to Hub and matching SDK source. Hub has not been officially released and its repository is private. Without access, explain the unavailable dependency and pause device installation. Do not request tokens in chat or change repository visibility.
3. If Hub exists but is incompatible, explain the differences and upgrade plan first and preserve existing data. Check the exact compatibility between Hub's bundled SDK and device firmware. Do not infer compatibility solely from an old README's minimum version, or automatically flash or replace firmware. NOTE4C is outside this app's scope.
4. The weather PNG output still needs adaptation for the device's grayscale display. Check whether the actual Hub interface accepts the format. If unsupported, clearly stop at the computer preview; do not invent an interface or silently switch to ZECTRIX Cloud push.

Installation and usage steps for this project:
1. Run the weather preview first: ask AI to create an isolated Python environment and start the local page using the repository instructions. Without a WeatherAPI Key, the first run shows clearly labeled sample data.
2. Connect your weather data: enter a WeatherAPI Key and city in the local page and check the observation time. The key stays on your computer. This is not a ZECTRIX Cloud API Key.
3. Export and display on the device: the current repository only generates images and has no device-push integration. Export a PNG first. To connect NOTE4, AI must separately check Hub, grayscale support and the image-push interface. A successful preview does not mean the device has displayed it.
For device push, adapt the Hub interface first. The connection layer uses the device SDK; downloading the SDK alone does not replace Hub. Check platform-specific paths, process management, build dependencies and speech backends, adapting as needed. Successful compilation does not verify cross-platform functionality.

First verification: Generate a 400×300 weather image and confirm the city, language and observation time. If device-push integration is incomplete, explicitly report that only the computer preview is done.
Report program startup, image generation, device reception and physical-screen verification separately. Do not treat successful simulation as real-device verification. Explain installation location, how to restart and stop, and limits when the computer or network disconnects.
Keep keys, Hub credentials, accounts and personal data in local configuration only, never shared tasks or logs. If this AI has no local execution environment, provide reviewable local installation steps first; do not claim installation is complete.