GenvexNabto
Library for local interfacing with HVAC systems running Genvex Connect or Nilan gateways. These systems are only officially cloud-accessible, but after extensive development, a local solution is now available.
Supported controller models
| Controller | Gateway required | Supported | Tested |
|---|---|---|---|
| Optima 250 | Yes, internet gateway | ✅ | ✅ |
| Optima 251 | Yes, internet gateway | ✅ | ✅ |
| Optima 260 | Yes, internet gateway | ✅ | |
| Optima 270 | Built in | ✅ | ✅ |
| Optima 301 | Yes, internet gateway | ✅ | ✅ |
| Optima 312 | Yes, internet gateway | ✅ | ✅ |
| Optima 314 | Built in | ✅ | |
| Nilan CTS400 | Yes, nilan gateway | ✅ | ✅ |
| Nilan CTS602 | Yes, nilan gateway | ✅ | ✅ |
| Nilan CTS602 Light | Yes, nilan gateway | ✅ | ✅ |
| Nilan CTS602 Geo | Yes, nilan gateway | ✅ |
For controllers that require a gateway, it is mandatory that the device supports Modbus. Note that Optima controllers delivered before 2014 may not have Modbus support.
How the libary works
Both Genvex Connect and Nilan gateways use the proprietary "Micro Nabto" protocol. Information about this protocol is limited, with most official documentation being removed from the internet following the companies' release of "Nabto Edge," which is largely incompatible with the older "Micro Nabto."
Typically, users connect via a dedicated app. The app loads a large, 6MB+ closed-source binary client for Nabto communication. A major limitation is that the binary is only available for Win32, Linux, Mac, Android, and iOS. There are no generic Linux ARM binaries, meaning implementing a Home Assistant custom component with these binaries would exclude widely used platforms like the Raspberry Pi.
The binary scans for available gateways by broadcasting a UDP packet. This packet either includes a specific device identifier or a wildcard (*) to request a response from any gateway. Gateways that are available will reply with their unique identifier over the same UDP IP and port to which the broadcast was sent.
While the normal connection process is handled online, it is encrypted and obfuscated. Significant progress has been made in reverse-engineering the online flow, leading to the discovery of a local connection method.
The local connection flow allows for direct communication with compatible gateways, using the user's email as the password.
Obligatory statement
The contributors are not responsible for any damages resulting from the use of this libary. No warranty is provided.
1 maintainer
Release files for genvexnabto 1.5.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| genvexnabto-1.5.4.tar.gz | 32.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| genvexnabto-1.5.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.0 kB
Release files / genvexnabto-1.5.4.tar.gz
| Download URL | genvexnabto-1.5.4.tar.gz |
|---|---|
| Size | 32.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9776903d1594cdf7b759df4d88233024dec660fa9d577e72892cb33e386ca33
|
|
BLAKE2b-256 checksum How to use checksums |
78521d9ddbd8ff2da4ae109a59f35ce296fb8653068e13e006afbbe8e07f0a9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 25, 2026.
Transparency logRelease files / genvexnabto-1.5.4-py3-none-any.whl
| Download URL | genvexnabto-1.5.4-py3-none-any.whl |
|---|---|
| Size | 42.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98e4bb79b6dfe0d6130558a1d5f3d7be4f20666304fa4f34a3a2ca476127e2c3
|
|
BLAKE2b-256 checksum How to use checksums |
6f4a23d64149a8e71d5d054ae06ed0e9f7ba1cb2b5fde938dab6d13885a4e16e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 25, 2026.
Transparency log
