Library for electricity meters Neva MT
Working via serial port or RFC2217 server. IEC 61107 protocol is used (currently IEC 62056-21) and OBIS codes.
Installation
python -m pip install pyneva
Usage examples
CLI
$ python -m pyneva connect -i rfc2217://192.168.88.109:1884 -m NevaMT324AOS --val active_energy current --obis 60.01.00*FF
Connected to: [NEVAMT324.1106 : 11111111]
Values:
total_energy ActiveEnergy(total=16484.51, T1=12896.28, T2=3588.23, T3=0.0, T4=0.0)
active_power ActivePower(phaseA=5.0, phaseB=1372.4, phaseC=122.3, total=1499.8)
OBIS:
60.01.00*FF 60089784
Code
from pyneva import NevaMT324AOS
# /dev/ttyX for linux local port
# comX or COMX for Windows local port
with NevaMT324AOS("rfc2217://192.168.88.109:1884") as meter:
print(meter.model)
# MT324 A OS 5(60)A
print(meter.serial_number)
# 11111111
print(meter.active_energy)
# ActiveEnergy(total=16348.84, T1=12790.08, T2=3558.76, T3=0.0, T4=0.0)
print(meter.voltage)
# Voltage(l1=233.81, l2=233.02, l3=232.15)
print(meter.active_power)
# ActivePower(l1=5.0, l2=1833.4, l3=130.3, total=1968.8)
print(meter.seasonal_schedules)
# (SeasonSchedule(month=1, day=1, weekday_skd_num=1, sat_skd_num=1, sun_skd_num=1),)
# Returns tuple with seasonal schedules.
# Each schedule specifies from which date the tariff starts,
# and the numbers of tariff schedules on weekdays, Saturdays, Sundays separately.
print(meter.special_days_schedules)
# ()
# Returns empty tuple if you have no special days tariff schedules (max 32 days).
print(meter.tariff_schedules)
# (
# TariffSchedule(parts=(
# TariffSchedulePart(hour=7, minute=0, T_num=1),
# TariffSchedulePart(hour=23, minute=0, T_num=2)
# )),
# )
# Returns tuple with tariff schedules.
# Each tariff schedule contains parts of the schedule.
# Each schedule part describes from what time of day the tariff starts
# and tariff number (T1, T2, T3, T4).
Supported models
- MT 324 A OS 5(60)A (NEVAMT324.11XX)
- MT 324 AR E4BS 5(60)A (NEVAMT324.25XX)
Metadata
Release files for pyneva 0.7.51
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 |
|---|---|---|---|---|
| pyneva-0.7.51.tar.gz | 13.0 kB | Without provenance | Details for pyneva-0.7.51.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyneva-0.7.51-py3-none-any.whl | Python 3 | none | any | Details for pyneva-0.7.51-py3-none-any.whl |
Total release size: 26.3 kB
Release files / pyneva-0.7.51.tar.gz
| Download URL | pyneva-0.7.51.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4881ff69605c2a9bdcc5469b7b8af6f7c9f68fbc1278392f64fff584e63b0bbd
|
|
BLAKE2b-256 checksum How to use checksums |
4b3f8df321eec0afd7d99d5231adf60a08a993e2a335f43acfcd4716ddce4455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Release files / pyneva-0.7.51-py3-none-any.whl
| Download URL | pyneva-0.7.51-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
558809bc4d7f21dc94ac34753e2a2b7b6d89003cb3fcc193a0af8b2848e57820
|
|
BLAKE2b-256 checksum How to use checksums |
beb7208796cba4e60584091167676e237768d186679e3e1214eab22b82d6da80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Security for pyneva 0.7.51
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.