Entrixy firmware — licenses, corresponding source and rebuilding
=============================================================

Original reference sketches are MIT licensed; see Entrixy-MIT.txt.
This does NOT relicense libraries, board cores, SDKs or user-written sketches.

Installed build components (31 October 2026):
  Arduino ESP32 core 3.3.6 (LGPL-2.1-or-later core; bundled components vary)
  Arduino ESP8266 core 3.1.2 (LGPL core; bundled components vary)
  WebSockets 2.7.2, Markus Sattler (LGPL-2.1-or-later)
  NimBLE-Arduino 2.2.3 (Apache-2.0 plus bundled component notices)
  ArduinoJson 7.4.3, Benoit Blanchon (MIT)

The exact installed core/library trees, including their individual notices,
are supplied in firmware-dependencies-20261031.zip in this directory.
Some SDK/toolchain files supplied by board vendors are binary components,
not original Entrixy code. Their included notices and upstream terms apply.

Rebuild a downloaded generated sketch:
  1. Install Arduino CLI from https://arduino.github.io/arduino-cli/.
  2. Install the matching board package with the versions above:
     arduino-cli core update-index --additional-urls \
       https://espressif.github.io/arduino-esp32/package_esp32_index.json,https://arduino.esp8266.com/stable/package_esp8266com_index.json
     arduino-cli core install esp32:esp32@3.3.6 --additional-urls \
       https://espressif.github.io/arduino-esp32/package_esp32_index.json
     arduino-cli core install esp8266:esp8266@3.1.2 --additional-urls \
       https://arduino.esp8266.com/stable/package_esp8266com_index.json
  3. Use the library sources in the dependency archive (including any local
     adaptations) in the Arduino user libraries directory. To modify an LGPL
     library, edit that source and compile again; there is no Entrixy signing
     requirement preventing you from flashing your own firmware.
  4. Download your build's source/rebuild archive from the configurator.
     It contains the generated sketch and the available build configuration,
     object/archive/link files and notices. Preserve your own Wi-Fi and device
     credentials: never publish this per-device archive.
  5. Put the sketch in a directory matching its .ino filename. Compile with
     the exact FQBN in BUILD-INFO.json:
       arduino-cli compile --fqbn '<FQBN>' --build-path ./build ./<sketch>
     The FQBN includes board options where applicable. The Arduino recipe in
     the matching core's platform.txt describes how objects and archives are
     linked; build.options.json records the actual build settings.
     Toolchain/SDK downloads use the corresponding core's package index.

Source upstreams:
  https://github.com/espressif/arduino-esp32/tree/3.3.6
  https://github.com/esp8266/Arduino/tree/3.1.2
  https://github.com/Links2004/arduinoWebSockets/tree/2.7.2
  https://github.com/h2zero/NimBLE-Arduino/tree/2.2.3
  https://github.com/bblanchon/ArduinoJson/tree/v7.4.3

Permission to modify and debug modifications of the LGPL-covered portions is
not restricted by the license of the original Entrixy reference sketches.
Retain all third-party notices when distributing firmware. A source-only
sketch ZIP is not a declaration that its compiled dependencies are all MIT.

For older cached builds without a per-build archive, download the generated
sketch and this dependency bundle. If the original build used a different
version or you need corresponding source/relink material that is absent,
contact hello@entrixy.com and identify the build/version without sending
credentials. Missing historical build material remains a release-audit item.
