Honeybee-PH:
Honeybee-PH is a free plugin for Ladybug Tools which enables users to add detailed "Passive House" style attributes to their models in addition to the normal Honeybee inputs. Both Passive House Institute (PHI) and Passive House Institute US (Phius) model data can be added to the Ladybug-Tools models using the plugin. Note that this plugin is in no way affiliated with or created by either the Passive House Institute (PHI) or the Passive House Institute US (Phius).
This plugin is designed to be used as a plugin for Ladybug-Tools v1.9 or higher. It can also be utilized by the Ladybug toolkit for building up models using Rhino 3D and Grasshopper using the honeybee_grasshopper_ph tools.
Packages:
-
honeybee_ph: Extend the basic Honeybee package with important new Passive House specific elements such as interior spaces and Passive House certification thresholds.
-
honeybee_energy_ph: Extend the Honeybee-Energy package with new Passive House style attributes for elements such as windows and construction assemblies (HVAC is migrating to
honeybee_phhvac). -
honeybee_phhvac: The dedicated Passive House HVAC model — ventilation, heating, heat-pumps, hot-water systems, ducting, and piping.
-
honeybee_ph_standards: Helpful new standards for programs and assemblies which are especially relevant to Passive House practitioners.
-
honeybee_ph_utils: Some additional misc. utilities used by the above packages.
Development:
- Requirements: Code must run under both IronPython 2.7 (the Rhino/Grasshopper runtime) and CPython 3.10+. See
context/CODING_STANDARDS.md. - Tests:
python3 -m coverage run && python3 -m coverage report(75% repository-wide coverage floor). - Agent/contributor orientation:
CLAUDE.mdand thecontext/folder (PRD, architecture, tech stack, coding standards).
More Information:
For more information on the use of these tools, check out the the Passive House Tools website: http://www.PassiveHouseTools.com
In most cases, once the detailed Passive House style data has been added to the Ladybug-Tools / Honeybee model, practitioners will then want to export the model data out to either the Passive House Planning Package (PHPP) or WUFI-Passive. The Passive House Exchange (PHX) library has been created for this purpose. For more information on model data input / output, see the PHX package.
1 maintainer
Metadata
1 maintainer
Release files for honeybee-ph 1.33.68
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| honeybee_ph-1.33.68.tar.gz | 169.1 kB | With provenance | Details for honeybee_ph-1.33.68.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| honeybee_ph-1.33.68-py3-none-any.whl | Python 3 | none | any | Details for honeybee_ph-1.33.68-py3-none-any.whl |
Total release size: 391.6 kB
Release files / honeybee_ph-1.33.68.tar.gz
| Download URL | honeybee_ph-1.33.68.tar.gz |
|---|---|
| Size | 169.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32cfd021141837f5941bc9efa0b8f60d22744169932a530b3b44a8ad47422629
|
|
BLAKE2b-256 checksum How to use checksums |
f446530859f05c3cca363d7d311e29bf4eb6166c85801944045c9194398c7259
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / honeybee_ph-1.33.68-py3-none-any.whl
| Download URL | honeybee_ph-1.33.68-py3-none-any.whl |
|---|---|
| Size | 222.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c16e24d014da65bd6a2badbf7893829aa5eed0a58fd9df4d4f2a4b3a7501fdc
|
|
BLAKE2b-256 checksum How to use checksums |
a1da1086862b01e19d0e11dfe2e4968e034b5f29b0b97d3b321448f01c60e52e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for honeybee-ph 1.33.68
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for honeybee_ph-1.33.68.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
