frequenz-api-common 0.0.1__tar.gz

frequenz-api-common-0.0.1/CODEOWNERS

@@ -0,0 +1,7 @@
+# Each line is a file pattern followed by one or more owners.
+# Owners will be requested for review when someone opens a pull request.
+
+# Fallback owner.
+# These are the default owners for everything in the repo, unless a later match
+# takes precedence.
+* @frequenz-floss/api-team

frequenz-api-common-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,82 @@
+Contributing to Frequenz Microgrid API
+======================================
+
+
+Build
+=====
+
+You can use `build` to simply build the source and binary distribution:
+
+```sh
+python -m pip install build
+python -m build
+```
+
+Local development
+=================
+
+You need to make sure you have the `git submodules` updated:
+
+```sh
+git submodule update --init
+```
+
+If you want to manually compile the proto files you need to install the build
+dependencies manually (sadly it seems like there is no way to install build
+dependencies from the `pyproject.toml` file with a simple command):
+
+```sh
+python -m pip install grpcio-tools mypy-protobuf setuptools setuptools_scm[toml] wheel
+```
+
+Then you can compile the proto files by running:
+
+```sh
+python setup.py compile_proto
+```
+
+If you have any issues with these dependencies, please check the
+`pyproject.toml` file and try installing the exact supported versions instead.
+
+
+Releasing
+=========
+
+These are the steps to create a new release:
+
+1. Get the latest head you want to create a release from.
+
+1. Update the `RELEASE_NOTES.md` file if it is not complete, up to date, and
+   clean from template comments (`<!-- ... ->`) and empty sections. Submit
+   a pull request if an update is needed, wait until it is merged, and update
+   the latest head you want to create a release from to get the new merged pull
+   request.
+
+3. Create a new signed tag using the release notes and
+   a [semver](https://semver.org/) compatible version number with a `v` prefix,
+   for example:
+
+   ```sh
+   git tag -s -F RELEASE_NOTES.md v0.0.1
+   ```
+
+4. Push the new tag.
+
+5. A GitHub action will test the tag and if all goes well it will create
+   a [GitHub
+   Release](https://github.com/frequenz-floss/frequenz-api-microgrid/releases),
+   create a new
+   [announcement](https://github.com/frequenz-floss/frequenz-api-microgrid/discussions/categories/announcements)
+   about the release, and upload a new package to
+   [PyPI](https://pypi.org/project/frequenz-api-microgrid/) automatically.
+
+6. Once this is done, reset the `RELEASE_NOTES.md` with the template:
+
+   ```sh
+   cp .github/RELEASE_NOTES.template.md RELEASE_NOTES.md
+   ```
+
+   Commit the new release notes and create a PR (this step should be automated
+   eventually too).
+
+7. Celebrate!

frequenz-api-common-0.0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 Frequenz Energy-as-a-Service GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

frequenz-api-common-0.0.1/MANIFEST.in

@@ -0,0 +1,7 @@
+exclude .gitignore
+exclude .gitmodules
+exclude noxfile.py
+recursive-exclude .github *
+recursive-exclude pytests *
+recursive-include py *.pyi
+recursive-include submodules/api-common-protos/google *.proto

frequenz-api-common-0.0.1/PKG-INFO

@@ -0,0 +1,30 @@
+Metadata-Version: 2.1
+Name: frequenz-api-common
+Version: 0.0.1
+Summary: Frequenz common gRPC API and bindings
+Author-email: Frequenz Energy-as-a-Service GmbH <floss@frequenz.com>
+License: MIT
+Project-URL: Changelog, https://github.com/frequenz-floss/frequenz-api-common/releases
+Project-URL: Repository, https://github.com/frequenz-floss/frequenz-api-common
+Project-URL: Issues, https://github.com/frequenz-floss/frequenz-api-common/issues
+Project-URL: Support, https://github.com/frequenz-floss/frequenz-api-common/discussions/categories/support
+Keywords: frequenz,api,microgrid,grpc,common
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: <4,>=3.11
+Description-Content-Type: text/markdown
+Provides-Extra: dev-docstrings
+Provides-Extra: dev-formatting
+Provides-Extra: dev-mypy
+Provides-Extra: dev-noxfile
+Provides-Extra: dev-pylint
+Provides-Extra: dev-pytest
+Provides-Extra: dev
+License-File: LICENSE
+
+# frequenz-api-common
+Common definitions for frequenz GRPC APIs

frequenz-api-common-0.0.1/README.md

@@ -0,0 +1,2 @@
+# frequenz-api-common
+Common definitions for frequenz GRPC APIs

frequenz-api-common-0.0.1/RELEASE_NOTES.md

@@ -0,0 +1,5 @@
+# Frequenz Common API Release Notes
+
+## Summary
+
+This is the first release, including packages for common metrics types, electrical metrics and components.

frequenz-api-common-0.0.1/proto/frequenz/api/common/components.proto

@@ -0,0 +1,117 @@
+// Frequenz microgrid components definitions.
+//
+// Copyright:
+// Copyright 2023 Frequenz Energy-as-a-Service GmbH
+//
+// License:
+// MIT
+
+syntax = "proto3";
+
+package frequenz.api.common.components;
+
+// Enumrated component categories.
+enum ComponentCategory {
+  // An unknown component categories, useful for error handling, and marking
+  // unknown components in a list of components with otherwise known categories.
+  COMPONENT_CATEGORY_UNSPECIFIED = 0;
+
+  // The point where the local microgrid is connected to the grid.
+  COMPONENT_CATEGORY_GRID = 1;
+
+  // A meter, for measuring electrical metrics, e.g., current, voltage, etc.
+  COMPONENT_CATEGORY_METER = 2;
+
+  // An electricity generator, with batteries or solar energy.
+  COMPONENT_CATEGORY_INVERTER = 3;
+
+  // A DC-DC converter.
+  COMPONENT_CATEGORY_CONVERTER = 4;
+
+  // A storage system for electrical energy, used by inverters.
+  COMPONENT_CATEGORY_BATTERY = 5;
+
+  // A station for charging electrical vehicles.
+  COMPONENT_CATEGORY_EV_CHARGER = 6;
+
+  // A sensor for measuring ambient metrics, e.g., temperature, humidity, etc.
+  COMPONENT_CATEGORY_SENSOR = 7;
+
+  // A crypto miner.
+  COMPONENT_CATEGORY_CRYPTO_MINER = 8;
+
+  // An electrolyzer for converting water into hydrogen and oxygen.
+  COMPONENT_CATEGORY_ELECTROLYZER = 9;
+
+  // A heat and power combustion plant (CHP stands for combined heat and power).
+  COMPONENT_CATEGORY_CHP = 10;
+}
+
+// Enumerated battery types.
+enum BatteryType {
+  // Unspecified.
+  BATTERY_TYPE_UNSPECIFIED = 0;
+
+  // Li-ion batteries.
+  BATTERY_TYPE_LI_ION = 1;
+
+  // Sodium-ion batteries
+  BATTERY_TYPE_NA_ION = 2;
+}
+
+// Enumerated inverter types.
+enum InverterType {
+  // Unspecified.
+  INVERTER_TYPE_UNSPECIFIED = 0;
+
+  // Battery inverter.
+  INVERTER_TYPE_BATTERY = 1;
+
+  // Solar inverter.
+  INVERTER_TYPE_SOLAR = 2;
+
+  // Hybrid inverter.
+  INVERTER_TYPE_HYBRID = 3;
+}
+
+// Enumerated EV charger types.
+enum EVChargerType {
+  // Default type.
+  EVCHARGER_TYPE_UNSPECIFIED = 0;
+
+  // The EV charging station supports AC charging only.
+  EVCHARGER_TYPE_AC = 1;
+
+  // The EV charging station supports DC charging only.
+  EVCHARGER_TYPE_DC = 2;
+
+  // The EV charging station supports both AC and DC.
+  EVCHARGER_TYPE_HYBRID = 3;
+}
+
+// Enumerated sensor types.
+enum SensorType {
+  // Unspecified
+  SENSOR_TYPE_UNSPECIFIED = 0;
+
+  // Thermometer (temperature sensor)
+  SENSOR_TYPE_THERMOMETER = 1;
+
+  // Hygrometer (humidity sensor)
+  SENSOR_TYPE_HYGROMETER = 2;
+
+  // Barometer (pressure sensor).
+  SENSOR_TYPE_BAROMETER = 3;
+
+  // Pyranometer (solar irradiance sensor).
+  SENSOR_TYPE_PYRANOMETER = 4;
+
+  // Anemometer (wind velocity and direction sensor).
+  SENSOR_TYPE_ANEMOMETER = 5;
+
+  // Accelerometers (acceleration sensor).
+  SENSOR_TYPE_ACCELEROMETER = 6;
+
+  // General sensors, which do not fall in any of the above categories
+  SENSOR_TYPE_GENERAL = 7;
+}

frequenz-api-common-0.0.1/proto/frequenz/api/common/metrics/electrical.proto

@@ -0,0 +1,199 @@
+// Contains definitions for electrical metrics (AC and DC).
+//
+// Copyright:
+// Copyright 2023 Frequenz Energy-as-a-Service GmbH
+//
+// License:
+// MIT
+
+syntax = "proto3";
+
+package frequenz.api.common.metrics.electrical;
+
+import "frequenz/api/common/metrics.proto";
+
+// Metrics of a DC electrical connection.
+message DC {
+  // The DC voltage across the component.
+  // In Volt (V).
+  metrics.Metric voltage = 1;
+
+  // The DC current flowing away from the grid connection.
+  // In passive sign convention:
+  // +ve current means consumption, away from the grid.
+  // -ve current means supply into the grid.
+  // In Ampere (A).
+  metrics.Metric current = 2;
+
+  // The DC power flowing away from the grid connection.
+  // In passive sign convention:
+  // +ve power means consumption, away from the grid.
+  // -ve power means supply into the grid.
+  // In Watt (W).
+  metrics.Metric power = 3;
+}
+
+// The current state and metrics of the electrical connections to the
+// inverter.
+message AC {
+  // The active energy the inverter is consuming or generating.
+  message ActiveEnergy {
+    // The sum of the consumed and delivered energy.
+    // This is a signed value in passive sign convention: if more energy is
+    // consumed than delivered, this is a -ve number, otherwise +ve.
+    // In Watt-hour (Wh).
+    metrics.Metric energy = 1;
+
+    // The consumed energy.
+    // In Watt-hour (Wh).
+    metrics.Metric energy_consumed = 2;
+
+    // The delivered energy.
+    // In Watt-hour (Wh).
+    metrics.Metric energy_delivered = 3;
+  }
+
+  // The reactive energy the inverter is consuming or generating.
+  message ReactiveEnergy {
+    // The sum of the capacitive and inductive energy.
+    // This is a signed value. If more energy is capacitive than inductive,
+    // this is a -ve number, otherwise +ve.
+    // In Volt-Ampere-hour (VArh).
+    metrics.Metric energy = 1;
+
+    // The capacitive energy.
+    // In Volt-Ampere-hour (VArh).
+    metrics.Metric energy_capacitive = 2;
+
+    // The inductive energy.
+    // In Volt-Ampere-hour (VArh).
+    metrics.Metric energy_inductive = 3;
+  }
+
+  // The harmonics of the fast Fourier transform of the instantaneous values
+  // and its total harmonic distortion.
+  // In percent (%).
+  message Harmonics {
+    float harmonic_1 = 1;
+    float harmonic_2 = 2;
+    float harmonic_3 = 3;
+    float harmonic_4 = 4;
+    float harmonic_5 = 5;
+    float harmonic_6 = 6;
+    float harmonic_7 = 7;
+    float harmonic_8 = 8;
+    float harmonic_9 = 9;
+    float harmonic_10 = 10;
+    float harmonic_11 = 11;
+  }
+
+  // AC metrics of a single phase.
+  message ACPhase {
+    // The AC voltage between the line and the neutral wire.
+    // In Volt (V).
+    metrics.Metric voltage = 1;
+
+    // AC current.
+    // +ve current means consumption, away from the grid.
+    // -ve current means supply into the grid.
+    // In Ampere (A).
+    metrics.Metric current = 2;
+
+    // AC active power.
+    // +ve power means consumption, away from the grid.
+    // -ve power means supply into the grid.
+    // In Watt (W).
+    metrics.Metric power_active = 3;
+
+    // AC reactive power.
+    // +ve power means inductive (leading).
+    // -ve power means capacitive (lagging).
+    // In Volt-Ampere reactive (VAr).
+    metrics.Metric power_reactive = 4;
+
+    // The total apparent energy. A Positive value represents the net apparent
+    // energy supplied to the grid connection, and vice versa.
+    // In Volt-Ampere-hour (VAh).
+    metrics.Metric energy_apparent = 5;
+
+    // The total active energy counters for the underlying component's
+    // consumption and supply.
+    // In Watt-hour (Wh).
+    ActiveEnergy energy_active = 6;
+
+    // The total reactive energy counters for the underlying component's
+    // capacitive and inductive energy values.
+    // In Volt-Ampere reactive hour (VArh).
+    ReactiveEnergy energy_reactive = 7;
+
+    // Harmonics of the instantaneous active power at the component.
+    // In percent (%).
+    Harmonics harmonics_power_active = 8;
+
+    // Total harmonic distortion
+    // of the instantaneous active power at the component.
+    // In percent (%).
+    float thd_power_active = 9;
+  }
+
+  // Overall AC metrics.
+
+  // The AC frequency.
+  // In Hertz (Hz).
+  metrics.Metric frequency = 1;
+
+  // The apparent 3-phase AC current. Positive values represent apparent energy
+  // flowing towards the grid connection, and vice versa.
+  // In Ampere (A).
+  metrics.Metric current = 2;
+
+  // The apparent 3-phase AC power. Positive values represent apparent energy
+  // flowing towards the grid connection, and vice versa.
+  // In Volt-Ampere (VA).
+  metrics.Metric power_apparent = 3;
+
+  // The total active 3-phase AC active power.
+  // +ve power means consumption, away from the grid.
+  // -ve power means supply into the grid.
+  // In Watt (W).
+  metrics.Metric power_active = 4;
+
+  // The reactive 3-phase AC power.
+  // +ve power means inductive (leading).
+  // -ve power means capacitive (lagging).
+  // In Volt-Ampere reactive (VAr).
+  metrics.Metric power_reactive = 5;
+
+  // The total 3-phase apparent energy. A positive value represents the net
+  // apparent energy supplied to the grid connection, and vice versa.
+  // In Volt-Ampere-hour (VAh).
+  metrics.Metric energy_apparent = 6;
+
+  // The total 3-phase active energy counters for the underlying component's
+  // consumption and supply.
+  // In Watt-hour (Wh).
+  ActiveEnergy energy_active = 7;
+
+  // The total 3-phase reactive energy counters for the underlying component's
+  // capacitive and inductive energy values.
+  // In Volt-Ampere reactive hour (VArh).
+  // FIXME: ReactiveEnergy says Volt-Ampere-hour (VAh).
+  ReactiveEnergy energy_reactive = 8;
+
+  // The sums of the harmonics
+  // of the instantaneous active power at the component across all 3 phases.
+  Harmonics harmonics_power_active = 9;
+
+  // The sums of the total harmonic distortion
+  // of the instantaneous active power at the component across all 3 phases.
+  float thd_power_active = 10;
+
+  // AC metrics for phase/line 1.
+  ACPhase phase_1 = 11;
+
+  // AC metrics for phase/line 2.
+  ACPhase phase_2 = 12;
+
+  // AC metrics for phase/line 3.
+  ACPhase phase_3 = 13;
+}

frequenz-api-common-0.0.1/proto/frequenz/api/common/metrics.proto

@@ -0,0 +1,92 @@
+// Metrics & bounds definitions.
+//
+// Copyright:
+// Copyright 2023 Frequenz Energy-as-a-Service GmbH
+//
+// License:
+// MIT
+
+syntax = "proto3";
+
+package frequenz.api.common.metrics;
+
+// A set of lower and upper bounds for any metric.
+// The units of the bounds are always the same as the related metric.
+message Bounds {
+  // The lower bound.
+  float lower = 1;
+
+  // The upper bound.
+  float upper = 2;
+}
+
+// A metric's value, with optional limits.
+message Metric {
+  // The current value of the metric.
+  float value = 1;
+
+  // The manufacturer's rated bounds of the metric. This may differ from
+  // `system_bounds` as it does not take into account the current state of the
+  // overall system.
+  Bounds rated_bounds = 2;
+
+  // The current bounds of the metric, as imposed by the component this metric
+  // originates from.
+  Bounds component_bounds = 3;
+
+  // These bounds indicate the range of values that are disallowed for the
+  // metric.
+  // If these bounds for a metric are [`lower`, `upper`], then this metric's
+  // `value` needs to comply with the constraints
+  // `value <= lower` OR `upper <= value`.
+  //
+  // It is important to note that these bounds work together with
+  // `system_inclusion_bounds`.
+  //
+  // E.g., for the system to accept a charge command,
+  // clients need to request power values within the bounds
+  // `[system_inclusion_bounds.lower, system_exclusion_bounds.lower]`.
+  // This means that clients can only request charge commands with values that
+  // are within the `system_inclusion_bounds`, but not within
+  // `system_exclusion_bounds`.
+  // Similarly, for the system to accept a discharge command,
+  // clients need to request power values within the bounds
+  // `[system_exclusion_bounds.upper, system_inclusion_bounds.upper]`.
+  //
+  // The following diagram illustrates the relationship between the bounds.
+  // ```
+  //   inclusion.lower                              inclusion.upper
+  // <-------|============|------------------|============|--------->
+  //                exclusion.lower    exclusion.upper
+  // ```
+  // ---- values here are disallowed and wil be rejected
+  // ==== vales here are allowed and will be accepted
+  Bounds system_exclusion_bounds = 4;
+
+  // These bounds indicate the range of values that are allowed for the metric.
+  // If these bounds for a metric are [`lower`, `upper`], then this metric's
+  // `value` needs to comply with the constraint `lower <= value <= upper`
+  //
+  // It is important to note that these bounds work together with
+  // `system_exclusion_bounds`.
+  //
+  // E.g., for the system to accept a charge command,
+  // clients need to request power values within the bounds
+  // `[system_inclusion_bounds.lower, system_exclusion_bounds.lower]`.
+  // This means that clients can only request charge commands with values that
+  // are within the `system_inclusion_bounds`, but not within
+  // `system_exclusion_bounds`.
+  // Similarly, for the system to accept a discharge command,
+  // clients need to request power values within the bounds
+  // `[system_exclusion_bounds.upper, system_inclusion_bounds.upper]`.
+  //
+  // The following diagram illustrates the relationship between the bounds.
+  // ```
+  //   inclusion.lower                              inclusion.upper
+  // <-------|============|------------------|============|--------->
+  //                exclusion.lower    exclusion.upper
+  // ```
+  // ---- values here are disallowed and wil be rejected
+  // ==== vales here are allowed and will be accepted
+  Bounds system_inclusion_bounds = 5;
+}

frequenz-api-common-0.0.1/py/frequenz/api/common/__init__.py

@@ -0,0 +1,4 @@
+# License: MIT
+# Copyright © 2023 Frequenz Energy-as-a-Service GmbH
+
+"""Frequenz Common API definitions."""

frequenz-api-common-0.0.1/py/frequenz/api/common/components_pb2.py

@@ -0,0 +1,33 @@
+# -*- coding: utf-8 -*-
+# Generated by the protocol buffer compiler.  DO NOT EDIT!
+# source: frequenz/api/common/components.proto
+"""Generated protocol buffer code."""
+from google.protobuf.internal import builder as _builder
+from google.protobuf import descriptor as _descriptor
+from google.protobuf import descriptor_pool as _descriptor_pool
+from google.protobuf import symbol_database as _symbol_database
+# @@protoc_insertion_point(imports)
+
+_sym_db = _symbol_database.Default()
+
+
+
+
+DESCRIPTOR = _descriptor_pool.Default().AddSerializedFile(b'\n$frequenz/api/common/components.proto\x12\x1e\x66requenz.api.common.components*\xfd\x02\n\x11\x43omponentCategory\x12\"\n\x1e\x43OMPONENT_CATEGORY_UNSPECIFIED\x10\x00\x12\x1b\n\x17\x43OMPONENT_CATEGORY_GRID\x10\x01\x12\x1c\n\x18\x43OMPONENT_CATEGORY_METER\x10\x02\x12\x1f\n\x1b\x43OMPONENT_CATEGORY_INVERTER\x10\x03\x12 \n\x1c\x43OMPONENT_CATEGORY_CONVERTER\x10\x04\x12\x1e\n\x1a\x43OMPONENT_CATEGORY_BATTERY\x10\x05\x12!\n\x1d\x43OMPONENT_CATEGORY_EV_CHARGER\x10\x06\x12\x1d\n\x19\x43OMPONENT_CATEGORY_SENSOR\x10\x07\x12#\n\x1f\x43OMPONENT_CATEGORY_CRYPTO_MINER\x10\x08\x12#\n\x1f\x43OMPONENT_CATEGORY_ELECTROLYZER\x10\t\x12\x1a\n\x16\x43OMPONENT_CATEGORY_CHP\x10\n*]\n\x0b\x42\x61tteryType\x12\x1c\n\x18\x42\x41TTERY_TYPE_UNSPECIFIED\x10\x00\x12\x17\n\x13\x42\x41TTERY_TYPE_LI_ION\x10\x01\x12\x17\n\x13\x42\x41TTERY_TYPE_NA_ION\x10\x02*{\n\x0cInverterType\x12\x1d\n\x19INVERTER_TYPE_UNSPECIFIED\x10\x00\x12\x19\n\x15INVERTER_TYPE_BATTERY\x10\x01\x12\x17\n\x13INVERTER_TYPE_SOLAR\x10\x02\x12\x18\n\x14INVERTER_TYPE_HYBRID\x10\x03*x\n\rEVChargerType\x12\x1e\n\x1a\x45VCHARGER_TYPE_UNSPECIFIED\x10\x00\x12\x15\n\x11\x45VCHARGER_TYPE_AC\x10\x01\x12\x15\n\x11\x45VCHARGER_TYPE_DC\x10\x02\x12\x19\n\x15\x45VCHARGER_TYPE_HYBRID\x10\x03*\xee\x01\n\nSensorType\x12\x1b\n\x17SENSOR_TYPE_UNSPECIFIED\x10\x00\x12\x1b\n\x17SENSOR_TYPE_THERMOMETER\x10\x01\x12\x1a\n\x16SENSOR_TYPE_HYGROMETER\x10\x02\x12\x19\n\x15SENSOR_TYPE_BAROMETER\x10\x03\x12\x1b\n\x17SENSOR_TYPE_PYRANOMETER\x10\x04\x12\x1a\n\x16SENSOR_TYPE_ANEMOMETER\x10\x05\x12\x1d\n\x19SENSOR_TYPE_ACCELEROMETER\x10\x06\x12\x17\n\x13SENSOR_TYPE_GENERAL\x10\x07\x62\x06proto3')
+
+_builder.BuildMessageAndEnumDescriptors(DESCRIPTOR, globals())
+_builder.BuildTopDescriptorsAndMessages(DESCRIPTOR, 'frequenz.api.common.components_pb2', globals())
+if _descriptor._USE_C_DESCRIPTORS == False:
+
+  DESCRIPTOR._options = None
+  _COMPONENTCATEGORY._serialized_start=73
+  _COMPONENTCATEGORY._serialized_end=454
+  _BATTERYTYPE._serialized_start=456
+  _BATTERYTYPE._serialized_end=549
+  _INVERTERTYPE._serialized_start=551
+  _INVERTERTYPE._serialized_end=674
+  _EVCHARGERTYPE._serialized_start=676
+  _EVCHARGERTYPE._serialized_end=796
+  _SENSORTYPE._serialized_start=799
+  _SENSORTYPE._serialized_end=1037
+# @@protoc_insertion_point(module_scope)