Category
Hardware Compatibility
Hardware
Other
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.17/HEAD
Description
@Quency-D It looks like since #8539 because the custom_meshtastic_* envs only get applied to env:heltec-v4 but not env:heltec-v4-tft, binaries don't get built for the expansion box product.
The same (unless Meshtastic adds a separate protobuf model ID for the TFT version) custom_meshtastic_* envs need to be added to heltec-v4-tft or moved to heltec-v4-base.
Relevant log output
Category
Hardware Compatibility
Hardware
Other
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.17/HEAD
Description
@Quency-D It looks like since #8539 because the custom_meshtastic_* envs only get applied to env:heltec-v4 but not env:heltec-v4-tft, binaries don't get built for the expansion box product.
The same (unless Meshtastic adds a separate protobuf model ID for the TFT version) custom_meshtastic_* envs need to be added to heltec-v4-tft or moved to heltec-v4-base.
Relevant log output