ize-compose

Ize Compose v1.4.0

Release date: 2026-06-13

This is the v1.4.0 release.

Use this build for the v1.4.0 WebServer, Wi-Fi browser page, and GitHub private repository sync flow.

Release Status

What Changed

Wi-Fi and WebServer Use

Use Network -> WiFi when the device should join an existing Wi-Fi network as a client. The device scans visible networks, connects to the selected SSID, shows its local IP address, and serves the unified browser page from that IP. Open the shown IP address from a phone or computer on the same network, then enter the PIN shown on the device.

Use Network -> WebServer when there is no trusted Wi-Fi network available or when direct device access is preferred. The device asks for a 10-digit numeric access-point password, starts the fixed IZEcompose_FileServer access point, and serves the same unified browser page at:

http://192.168.4.1/

The WebServer password stays visible on the device until the browser PIN is accepted. WebServer automatic shutdown tracking starts only after PIN authentication. After that authenticated client session has existed, WebServer mode shuts down when connected clients disappear for more than 2 seconds. Use Ctrl + Menu to exit manually.

Required SD Card Files

Prepare these files on the SD card:

/ize_compose/ize_compose_1-4-0.html
/ize_compose/initial.png
/ize_compose/hwalja/hwalja_latin.bin
/ize_compose/hwalja/hwalja_hangul.bin
/ize_compose/hwalja/hwalja_jamo.bin

Recommended additional font files:

/ize_compose/hwalja/hwalja_jp.bin
/ize_compose/hwalja/hwalja_greek_cyrillic.bin
/ize_compose/hwalja/hwalja_arabic.bin
/ize_compose/hwalja/hwalja_indic.bin
/ize_compose/hwalja/hwalja_sea.bin
/ize_compose/hwalja/hwalja_misc.bin

Generated files:

/ize_compose/settings_backup.json
/ize_compose/upload/izefirmware.bin

settings_backup.json is written by the firmware as a settings backup. upload/izefirmware.bin is an internal staged firmware file used during SD OTA update. Neither file needs to be prepared manually for a normal install.

There is no repository-side documents/index.html file in this release.

GitHub Private Repository Setup

1. Create a private repository

  1. Open GitHub in a browser.
  2. Click New repository.
  3. Set Owner to the account or organization that should own the backup repository.
  4. Enter a repository name, for example:

    ize-compose-documents
    
  5. Select Private.
  6. Create the repository.
  7. Keep the default branch name. Most new repositories use:

    main
    
  8. If GitHub asks whether to add a README, either choice is acceptable.

The firmware creates the configured document path when it uploads documents. GitHub does not store empty folders, so you do not need to prepare an empty documents folder manually.

2. Create a GitHub token

The device needs a token because the repository is private and GitHub requires API authentication for reading and writing repository contents.

Recommended token type:

Fine-grained personal access token

Steps:

  1. Open GitHub.
  2. Go to Settings.
  3. Open Developer settings.
  4. Open Personal access tokens.
  5. Choose Fine-grained tokens.
  6. Create a new token.
  7. Set the token owner to the same account or organization that owns the repository.
  8. Under Repository access, choose Only select repositories.
  9. Select the private repository created above.
  10. Under Repository permissions, set:

    Contents: Read and write
    Metadata: Read-only
    
  11. Generate the token.
  12. Copy the token immediately. GitHub will not show it again.

3. Enter GitHub settings on Ize Compose

  1. Install this firmware.
  2. Make sure this SD card file exists:

    /ize_compose/ize_compose_1-4-0.html
    
  3. On the device, open:

    Menu -> Network -> WiFi
    
  4. Select a visible Wi-Fi network.
  5. Enter the Wi-Fi password if required.
  6. After connection, the device shows a local IP address.
  7. Open that IP address from a computer or phone on the same Wi-Fi network.
  8. Enter the PIN shown on the device.
  9. Scroll to GitHub Sync.
  10. Fill in:

    Owner:       your GitHub account or organization
    Repository:  repository name only
    Branch:      main
    Path:        documents
    Token:       the token copied from GitHub
    
  11. Click Save GitHub Settings.
  12. Leave Wi-Fi mode with Ctrl + Menu.

4. Run sync from the device

After GitHub settings have been saved once:

  1. Open the device menu.
  2. Select:

    Sync
    
  3. The device should connect to the last successful Wi-Fi network.
  4. The device should sync local .txt documents with the configured repository path.
  5. The device should show whether sync completed or failed.
  6. The device should turn Wi-Fi off and return to the menu.

GitHub Sync Rules

Troubleshooting

GitHub repository info missing

The device does not have complete GitHub settings. Re-enter Network -> WiFi, open the browser page, and save Owner, Repository, Branch, Path, and Token.

Saved Wi-Fi not found

The last successful Wi-Fi network is not visible. Re-enter Network -> WiFi, connect to the desired network again, then try Sync.

Token rejected

Check:

Files created on GitHub disappear

This is expected. The device owns document creation and numbering. Create new documents on the device or upload .txt files through the device Wi-Fi/WebServer unified page.

Files deleted on GitHub come back

This is expected if the SD card still has the matching document. Delete from the device when the deletion should sync to both sides.

Verification

Firmware:

firmware/izefirmware.bin
Size: 1,256,112 bytes
SHA-256: EE22CA511686DB14404189B93C63128E2EF0AB6387EAAF51EB46993BA94073E6

Upgrade Notes

  1. Upload firmware/izefirmware.bin.
  2. Copy the unified browser page to the SD card:

    /ize_compose/ize_compose_1-4-0.html
    
    
  3. Keep or restore font files under:

    /ize_compose/hwalja/
    
  4. Reboot after update.
  5. Confirm that the Settings & Update tab shows:

    v1.4.0
    

v1.4.0 unified web change

Online update completion