Skip to main content

NiPPE - Nibe Power Performance Enhancement

Prerequisites

Open in Container

  1. Clone the repository to your local machine
  2. Open the repository in VSCode
  3. A window will pop up in the lower left corner, asking if you want to open the repository in a container. Click "Reopen in Container" (OR press F1 and type "Remote-Containers: Reopen in Container")

Formatting

Formatting is strictly done by Black and the project is setup to automatically format on save.

Versioning

Versioning follows SemVer and is handled automatically by setuptools-git-versioning together with tags.

To get the current version you can run setuptools-git-versioning in a terminal inside of the repo.

Testing

We encourage you to provide unit tests for your code contributions.

The tests should be added in the tests/ folder and can be run by executing pytest in a terminal.

Tests can also be run through VSCodes Command Palette or Test Explorer.

Building code for ESP device

  1. Install ESP-IDF extension in VSCode

  2. Install ESPHome locally

  3. Change ssid and password to match your wifi in the nippegw.yaml file in the root of the project

  4. Run esphome -v compile nippegw.yaml in the root of the project which will probably fail with the following message

    image

  5. Copy the argument from the last 3 rows in the above picture i.e.

    --chip esp32c3 merge_bin -o C:\reps\git\nippe\.esphome\build\nippegw\.pioenvs\nippegw/firmware-factory.bin --flash_size 4MB 0x0000 C:\Users\bt6259\.platformio\packages\framework-arduinoespressif32\tools\sdk\esp32c3\bin\bootloader__40m.bin 0x8000 C:\reps\git\nippe\.esphome\build\nippegw\.pioenvs\nippegw\partitions.bin 0xe000 C:\Users\bt6259\.platformio\packages\framework-arduinoespressif32\tools\partitions\boot_app0.bin 0x10000 C:\reps\git\nippe\.esphome\build\nippegw\.pioenvs\nippegw/firmware.bin
    
  6. Make the following change to the copied text (above = before, below = after)

    image

  7. Run the following

    esptool.exe <Your copied text>
    

    in the root of the project, this will generate a binary for you to upload to the esp device.

  8. Hold the "EN" button on the esp device and connect it to your computer via USB

  9. Open device manager to find the COM port that the device is connected to (in our case COM9)

    image

  10. Run the following command in the root of the project to flash the device

    esptool.exe --port <Your COM port> write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x0 .\.esphome\build\nippegw\.pioenvs\nippegw\firmware-factory.bin
    
  11. Press the "BOOT" button on the esp device to load the new firmware, the device will show up as a wifi called "nippegw" in your wifi list

Metadata

Release files for nippe 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nippe 0.0.3
File Size Uploaded Provenance
nippe-0.0.3.tar.gz 15.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for nippe 0.0.3
File Interpreter ABI Platform
nippe-0.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 30.8 kB

Release files / nippe-0.0.3.tar.gz

Download URL nippe-0.0.3.tar.gz
Size 15.5 kB
Tags Source
SHA-256 checksum
How to use checksums
c3e61d46476659570399decb199697b8e1bd24a08f9ee051242ef52c8d60eca1
BLAKE2b-256 checksum
How to use checksums
accc7fe12e78950a86b7c15a01a0cb45993cfd4a24e4ac364e081e4d30c1983a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.16

Release files / nippe-0.0.3-py3-none-any.whl

Download URL nippe-0.0.3-py3-none-any.whl
Size 15.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bec164e3072d56c2876f26028806f14953fcce4156a1031d6147fb36c48bb0c8
BLAKE2b-256 checksum
How to use checksums
0281836c7e5e1d83af808ba8dbadfbd6c8290fc75e31918a8a6a95462bf47fb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.16

Security for nippe 0.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.0.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page