Python Wrapper for Meteobridge Datalogger
This module communicates with a Meteobridge Datalogger using their Template Script.
The module is primarily written for the purpose of being used in Home Assistant for the Custom Integration called meteobridge but might be used for other purposes also.
Install
pymeteobridgedata is avaible on PyPi:
pip install pymeteobridgedata
Usage
This library is primarily designed to be used in an async context.
The main interface for the library is the pymeteobridgedata.MeteobridgeApiClient. This interface takes 6 options:
username: (required) The username to login to your Meteobridge device. Default this meteobridge.password: (required) The password for your meteobridge device.ip_address: (required) IP Address of the Meteobridge device.units: (optional) Valid options here are metric or imperial. Metebridge devices always deliver data in metric units, so conversion will only take place if if metric is not selected. Default value is metricextra_sensors: (optional) Number of extra sensors attached to the Meteobridge Logger (Default is 0, max is 7)homeassistant: (optional) Valid options are True or False. If set to True, there will be some unit types that will not be converted, as Home Assistant will take care of that. Default value is True
Example Python script
import asyncio
import logging
import time
from pymeteobridgedata import MeteobridgeApiClient, Invalid, NotAuthorized, BadRequest
from pymeteobridgedata.data import DataLoggerDescription, ObservationDescription
_LOGGER = logging.getLogger(__name__)
async def main() -> None:
logging.basicConfig(level=logging.DEBUG)
start = time.time()
meteobridge = MeteobridgeApiClient(USERNAME, PASSWORD, IP_ADDRESS, homeassistant=False, units="imperial", extra_sensors=0)
try:
await meteobridge.initialize()
except Invalid as err:
_LOGGER.debug(err)
except NotAuthorized as err:
_LOGGER.debug(err)
except BadRequest as err:
_LOGGER.debug(err)
data: DataLoggerDescription = meteobridge.device_data
if data is not None:
for field in data.__dataclass_fields__:
value = getattr(data, field)
print(field,"-", value)
data: ObservationDescription = await meteobridge.update_observations()
if data is not None:
for field in data.__dataclass_fields__:
value = getattr(data, field)
print(field,"-", value)
end = time.time()
await meteobridge.req.close()
_LOGGER.info("Execution time: %s seconds", end - start)
asyncio.run(main())
Release files for pymeteobridgedata 0.1.23
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pymeteobridgedata-0.1.23.tar.gz | 15.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pymeteobridgedata-0.1.23-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.2 kB
Release files / pymeteobridgedata-0.1.23.tar.gz
| Download URL | pymeteobridgedata-0.1.23.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
296965b3c0ace3cc9b21bce294d6ca0cfe03e4b35e2ac841ae19f6186f877b0a
|
|
BLAKE2b-256 checksum How to use checksums |
fa6622e791cf5bcdb1cfdcb516795fcf0f3a69602435eabf1df0a397835c0bed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 7, 2026.
Transparency logRelease files / pymeteobridgedata-0.1.23-py3-none-any.whl
| Download URL | pymeteobridgedata-0.1.23-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efc18c44fae409f1d6b0e39f327692b06f328c043d2b8237c3e1630889f223b8
|
|
BLAKE2b-256 checksum How to use checksums |
d1f6dd9e5846331abc9c91fed323fd6ecf585225c6b9535c1e54feeec23fb585
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 7, 2026.
Transparency log