arthexis 0.1.23__tar.gz → 0.1.25__tar.gz

{arthexis-0.1.23 → arthexis-0.1.25}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: arthexis
-Version: 0.1.23
+Version: 0.1.25
 Summary: Power & Energy Infrastructure
 Author-email: "Rafael J. Guillén-Osorio" <tecnologia@gelectriic.com>
 License-Expression: GPL-3.0-only
@@ -15,7 +15,7 @@ Requires-Dist: amqp==5.3.1
 Requires-Dist: annotated-types==0.7.0
 Requires-Dist: anyio==4.9.0
 Requires-Dist: asgiref==3.10.0
-Requires-Dist: atproto==0.0.62
+Requires-Dist: atproto<0.1.0,>=0.0.63
 Requires-Dist: attrs==25.3.0
 Requires-Dist: autobahn==24.4.2
 Requires-Dist: Automat==25.4.16
@@ -48,6 +48,7 @@ Requires-Dist: django-timezone-field==7.1
 Requires-Dist: dnspython==2.7.0
 Requires-Dist: docutils==0.22.2
 Requires-Dist: gpiozero==2.0.1; sys_platform == "linux"
+Requires-Dist: graphene-django==3.2.2
 Requires-Dist: graphviz==0.21
 Requires-Dist: h11==0.16.0
 Requires-Dist: httpcore==1.0.9
@@ -70,8 +71,8 @@ Requires-Dist: psycopg-binary==3.2.12
 Requires-Dist: pyasn1==0.6.1
 Requires-Dist: pyasn1_modules==0.4.2
 Requires-Dist: pycparser==2.22
-Requires-Dist: pydantic==2.11.7
-Requires-Dist: pydantic_core==2.33.2
+Requires-Dist: pydantic==2.12.3
+Requires-Dist: pydantic_core==2.41.4
 Requires-Dist: pyOpenSSL==25.1.0
 Requires-Dist: pyperclip==1.11.0
 Requires-Dist: PySocks==1.7.1
@@ -106,7 +107,7 @@ Requires-Dist: vine==5.1.0
 Requires-Dist: wcwidth==0.2.14
 Requires-Dist: webencodings==0.5.1
 Requires-Dist: websocket-client==1.8.0
-Requires-Dist: websockets==13.1
+Requires-Dist: websockets==15.0.1
 Requires-Dist: whitenoise==6.11.0
 Requires-Dist: plyer==2.1.0; sys_platform == "win32"
 Requires-Dist: wsproto==1.2.0
@@ -124,19 +125,39 @@ Arthexis Constellation is a [narrative-driven](https://en.wikipedia.org/wiki/Nar
 
 ## Current Features
 
-- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system, handling:
-  - Lifecycle & sessions
-    - `BootNotification`
-    - `Heartbeat`
-    - `StatusNotification`
-    - `StartTransaction`
-    - `StopTransaction`
-  - Access & metering
-    - `Authorize`
-    - `MeterValues`
-  - Maintenance & firmware
-    - `DiagnosticsStatusNotification`
-    - `FirmwareStatusNotification`
+- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system. Supported actions are summarized below.
+
+  **Charge point → CSMS**
+
+  | Action | What we do |
+  | --- | --- |
+  | `Authorize` | Validate RFID or token authorization requests before a session starts. |
+  | `BootNotification` | Register the charge point and update identity, firmware, and status details. |
+  | `DataTransfer` | Accept vendor-specific payloads and record the results. |
+  | `DiagnosticsStatusNotification` | Track the progress of diagnostic uploads kicked off from the back office. |
+  | `FirmwareStatusNotification` | Track firmware update lifecycle events from charge points. |
+  | `Heartbeat` | Keep the websocket session alive and update last-seen timestamps. |
+  | `MeterValues` | Persist periodic energy and power readings while a transaction is active. |
+  | `StartTransaction` | Create charging sessions with initial meter values and identification data. |
+  | `StatusNotification` | Reflect connector availability and fault states in real time. |
+  | `StopTransaction` | Close charging sessions, capturing closing meter values and stop reasons. |
+
+  **CSMS → Charge point**
+
+  | Action | What we do |
+  | --- | --- |
+  | `ChangeAvailability` | Switch connectors or the whole station between operative and inoperative states. |
+  | `DataTransfer` | Send vendor-specific commands and log the charge point response. |
+  | `GetConfiguration` | Poll the device for the current values of tracked configuration keys. |
+  | `RemoteStartTransaction` | Initiate a charging session remotely for an identified customer or token. |
+  | `RemoteStopTransaction` | Terminate active charging sessions from the control center. |
+  | `ReserveNow` | Reserve connectors for upcoming sessions with automatic connector selection and confirmation tracking. |
+  | `Reset` | Request a soft or hard reboot to recover from faults. |
+  | `TriggerMessage` | Ask the device to send an immediate update (for example status or diagnostics). |
+
+  **OCPP 1.6 roadmap.** The following catalogue actions are in our backlog: `CancelReservation`, `ChangeConfiguration`, `ClearCache`, `ClearChargingProfile`, `GetCompositeSchedule`, `GetDiagnostics`, `GetLocalListVersion`, `SendLocalList`, `SetChargingProfile`, `UnlockConnector`, `UpdateFirmware`.
+
+- Charge point reservations with automated connector assignment, energy account and RFID linkage, and EVCS confirmation tracking.
 - [API](https://en.wikipedia.org/wiki/API) integration with [Odoo](https://www.odoo.com/), syncing:
   - Employee credentials via `res.users`
   - Product catalog lookups via `product.product`

{arthexis-0.1.23 → arthexis-0.1.25}/README.md

@@ -9,19 +9,39 @@ Arthexis Constellation is a [narrative-driven](https://en.wikipedia.org/wiki/Nar
 
 ## Current Features
 
-- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system, handling:
-  - Lifecycle & sessions
-    - `BootNotification`
-    - `Heartbeat`
-    - `StatusNotification`
-    - `StartTransaction`
-    - `StopTransaction`
-  - Access & metering
-    - `Authorize`
-    - `MeterValues`
-  - Maintenance & firmware
-    - `DiagnosticsStatusNotification`
-    - `FirmwareStatusNotification`
+- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system. Supported actions are summarized below.
+
+  **Charge point → CSMS**
+
+  | Action | What we do |
+  | --- | --- |
+  | `Authorize` | Validate RFID or token authorization requests before a session starts. |
+  | `BootNotification` | Register the charge point and update identity, firmware, and status details. |
+  | `DataTransfer` | Accept vendor-specific payloads and record the results. |
+  | `DiagnosticsStatusNotification` | Track the progress of diagnostic uploads kicked off from the back office. |
+  | `FirmwareStatusNotification` | Track firmware update lifecycle events from charge points. |
+  | `Heartbeat` | Keep the websocket session alive and update last-seen timestamps. |
+  | `MeterValues` | Persist periodic energy and power readings while a transaction is active. |
+  | `StartTransaction` | Create charging sessions with initial meter values and identification data. |
+  | `StatusNotification` | Reflect connector availability and fault states in real time. |
+  | `StopTransaction` | Close charging sessions, capturing closing meter values and stop reasons. |
+
+  **CSMS → Charge point**
+
+  | Action | What we do |
+  | --- | --- |
+  | `ChangeAvailability` | Switch connectors or the whole station between operative and inoperative states. |
+  | `DataTransfer` | Send vendor-specific commands and log the charge point response. |
+  | `GetConfiguration` | Poll the device for the current values of tracked configuration keys. |
+  | `RemoteStartTransaction` | Initiate a charging session remotely for an identified customer or token. |
+  | `RemoteStopTransaction` | Terminate active charging sessions from the control center. |
+  | `ReserveNow` | Reserve connectors for upcoming sessions with automatic connector selection and confirmation tracking. |
+  | `Reset` | Request a soft or hard reboot to recover from faults. |
+  | `TriggerMessage` | Ask the device to send an immediate update (for example status or diagnostics). |
+
+  **OCPP 1.6 roadmap.** The following catalogue actions are in our backlog: `CancelReservation`, `ChangeConfiguration`, `ClearCache`, `ClearChargingProfile`, `GetCompositeSchedule`, `GetDiagnostics`, `GetLocalListVersion`, `SendLocalList`, `SetChargingProfile`, `UnlockConnector`, `UpdateFirmware`.
+
+- Charge point reservations with automated connector assignment, energy account and RFID linkage, and EVCS confirmation tracking.
 - [API](https://en.wikipedia.org/wiki/API) integration with [Odoo](https://www.odoo.com/), syncing:
   - Employee credentials via `res.users`
   - Product catalog lookups via `product.product`

{arthexis-0.1.23 → arthexis-0.1.25}/arthexis.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: arthexis
-Version: 0.1.23
+Version: 0.1.25
 Summary: Power & Energy Infrastructure
 Author-email: "Rafael J. Guillén-Osorio" <tecnologia@gelectriic.com>
 License-Expression: GPL-3.0-only
@@ -15,7 +15,7 @@ Requires-Dist: amqp==5.3.1
 Requires-Dist: annotated-types==0.7.0
 Requires-Dist: anyio==4.9.0
 Requires-Dist: asgiref==3.10.0
-Requires-Dist: atproto==0.0.62
+Requires-Dist: atproto<0.1.0,>=0.0.63
 Requires-Dist: attrs==25.3.0
 Requires-Dist: autobahn==24.4.2
 Requires-Dist: Automat==25.4.16
@@ -48,6 +48,7 @@ Requires-Dist: django-timezone-field==7.1
 Requires-Dist: dnspython==2.7.0
 Requires-Dist: docutils==0.22.2
 Requires-Dist: gpiozero==2.0.1; sys_platform == "linux"
+Requires-Dist: graphene-django==3.2.2
 Requires-Dist: graphviz==0.21
 Requires-Dist: h11==0.16.0
 Requires-Dist: httpcore==1.0.9
@@ -70,8 +71,8 @@ Requires-Dist: psycopg-binary==3.2.12
 Requires-Dist: pyasn1==0.6.1
 Requires-Dist: pyasn1_modules==0.4.2
 Requires-Dist: pycparser==2.22
-Requires-Dist: pydantic==2.11.7
-Requires-Dist: pydantic_core==2.33.2
+Requires-Dist: pydantic==2.12.3
+Requires-Dist: pydantic_core==2.41.4
 Requires-Dist: pyOpenSSL==25.1.0
 Requires-Dist: pyperclip==1.11.0
 Requires-Dist: PySocks==1.7.1
@@ -106,7 +107,7 @@ Requires-Dist: vine==5.1.0
 Requires-Dist: wcwidth==0.2.14
 Requires-Dist: webencodings==0.5.1
 Requires-Dist: websocket-client==1.8.0
-Requires-Dist: websockets==13.1
+Requires-Dist: websockets==15.0.1
 Requires-Dist: whitenoise==6.11.0
 Requires-Dist: plyer==2.1.0; sys_platform == "win32"
 Requires-Dist: wsproto==1.2.0
@@ -124,19 +125,39 @@ Arthexis Constellation is a [narrative-driven](https://en.wikipedia.org/wiki/Nar
 
 ## Current Features
 
-- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system, handling:
-  - Lifecycle & sessions
-    - `BootNotification`
-    - `Heartbeat`
-    - `StatusNotification`
-    - `StartTransaction`
-    - `StopTransaction`
-  - Access & metering
-    - `Authorize`
-    - `MeterValues`
-  - Maintenance & firmware
-    - `DiagnosticsStatusNotification`
-    - `FirmwareStatusNotification`
+- Compatible with the [Open Charge Point Protocol (OCPP) 1.6](https://www.openchargealliance.org/protocols/ocpp-16/) central system. Supported actions are summarized below.
+
+  **Charge point → CSMS**
+
+  | Action | What we do |
+  | --- | --- |
+  | `Authorize` | Validate RFID or token authorization requests before a session starts. |
+  | `BootNotification` | Register the charge point and update identity, firmware, and status details. |
+  | `DataTransfer` | Accept vendor-specific payloads and record the results. |
+  | `DiagnosticsStatusNotification` | Track the progress of diagnostic uploads kicked off from the back office. |
+  | `FirmwareStatusNotification` | Track firmware update lifecycle events from charge points. |
+  | `Heartbeat` | Keep the websocket session alive and update last-seen timestamps. |
+  | `MeterValues` | Persist periodic energy and power readings while a transaction is active. |
+  | `StartTransaction` | Create charging sessions with initial meter values and identification data. |
+  | `StatusNotification` | Reflect connector availability and fault states in real time. |
+  | `StopTransaction` | Close charging sessions, capturing closing meter values and stop reasons. |
+
+  **CSMS → Charge point**
+
+  | Action | What we do |
+  | --- | --- |
+  | `ChangeAvailability` | Switch connectors or the whole station between operative and inoperative states. |
+  | `DataTransfer` | Send vendor-specific commands and log the charge point response. |
+  | `GetConfiguration` | Poll the device for the current values of tracked configuration keys. |
+  | `RemoteStartTransaction` | Initiate a charging session remotely for an identified customer or token. |
+  | `RemoteStopTransaction` | Terminate active charging sessions from the control center. |
+  | `ReserveNow` | Reserve connectors for upcoming sessions with automatic connector selection and confirmation tracking. |
+  | `Reset` | Request a soft or hard reboot to recover from faults. |
+  | `TriggerMessage` | Ask the device to send an immediate update (for example status or diagnostics). |
+
+  **OCPP 1.6 roadmap.** The following catalogue actions are in our backlog: `CancelReservation`, `ChangeConfiguration`, `ClearCache`, `ClearChargingProfile`, `GetCompositeSchedule`, `GetDiagnostics`, `GetLocalListVersion`, `SendLocalList`, `SetChargingProfile`, `UnlockConnector`, `UpdateFirmware`.
+
+- Charge point reservations with automated connector assignment, energy account and RFID linkage, and EVCS confirmation tracking.
 - [API](https://en.wikipedia.org/wiki/API) integration with [Odoo](https://www.odoo.com/), syncing:
   - Employee credentials via `res.users`
   - Product catalog lookups via `product.product`

{arthexis-0.1.23 → arthexis-0.1.25}/arthexis.egg-info/SOURCES.txt

@@ -83,6 +83,7 @@ ocpp/consumers.py
 ocpp/evcs.py
 ocpp/evcs_discovery.py
 ocpp/models.py
+ocpp/network.py
 ocpp/reference_utils.py
 ocpp/routing.py
 ocpp/simulator.py
@@ -147,6 +148,7 @@ tests/test_email_outbox_admin.py
 tests/test_email_profiles.py
 tests/test_email_transaction.py
 tests/test_env_refresh_clean.py
+tests/test_env_refresh_dependency_conflict.py
 tests/test_env_refresh_pip.py
 tests/test_env_refresh_unlink.py
 tests/test_experience_admin_group.py

{arthexis-0.1.23 → arthexis-0.1.25}/arthexis.egg-info/requires.txt

@@ -2,7 +2,7 @@ amqp==5.3.1
 annotated-types==0.7.0
 anyio==4.9.0
 asgiref==3.10.0
-atproto==0.0.62
+atproto<0.1.0,>=0.0.63
 attrs==25.3.0
 autobahn==24.4.2
 Automat==25.4.16
@@ -34,6 +34,7 @@ django-otp==1.5.4
 django-timezone-field==7.1
 dnspython==2.7.0
 docutils==0.22.2
+graphene-django==3.2.2
 graphviz==0.21
 h11==0.16.0
 httpcore==1.0.9
@@ -55,8 +56,8 @@ psycopg-binary==3.2.12
 pyasn1==0.6.1
 pyasn1_modules==0.4.2
 pycparser==2.22
-pydantic==2.11.7
-pydantic_core==2.33.2
+pydantic==2.12.3
+pydantic_core==2.41.4
 pyOpenSSL==25.1.0
 pyperclip==1.11.0
 PySocks==1.7.1
@@ -91,7 +92,7 @@ vine==5.1.0
 wcwidth==0.2.14
 webencodings==0.5.1
 websocket-client==1.8.0
-websockets==13.1
+websockets==15.0.1
 whitenoise==6.11.0
 wsproto==1.2.0
 zope.interface==8.0.1

{arthexis-0.1.23 → arthexis-0.1.25}/config/settings.py

@@ -18,6 +18,8 @@ import ipaddress
 import socket
 from core.log_paths import select_log_dir
 from django.utils.translation import gettext_lazy as _
+from datetime import timedelta
+
 from celery.schedules import crontab
 from django.http import request as http_request
 from django.http.request import split_domain_port
@@ -333,6 +335,7 @@ CsrfViewMiddleware._check_referer = _check_referer_with_forwarded
 # Application definition
 
 LOCAL_APPS = [
+    "api",
     "nodes",
     "core",
     "ocpp",
@@ -666,4 +669,8 @@ CELERY_BEAT_SCHEDULE = {
         "task": "ocpp.tasks.schedule_daily_charge_point_configuration_checks",
         "schedule": crontab(minute=0, hour=0),
     },
+    "ocpp_forwarding_push": {
+        "task": "ocpp.tasks.push_forwarded_charge_points",
+        "schedule": timedelta(seconds=5),
+    },
 }

{arthexis-0.1.23 → arthexis-0.1.25}/config/urls.py

@@ -20,6 +20,7 @@ from django.views.decorators.csrf import csrf_exempt
 from django.views.generic import RedirectView
 from django.views.i18n import set_language
 from django.utils.translation import gettext_lazy as _
+from api.views import EnergyGraphQLView
 from core import views as core_views
 from core.admindocs import (
     CommandsView,
@@ -119,6 +120,7 @@ urlpatterns = [
         name="admin-model-graph",
     ),
     path("version/", core_views.version_info, name="version-info"),
+    path("graphql/", EnergyGraphQLView.as_view(), name="graphql"),
     path(
         "admin/core/releases/<int:pk>/<str:action>/",
         core_views.release_progress,