Skip to content

Conversation

@TCWORLD
Copy link
Contributor

@TCWORLD TCWORLD commented Nov 13, 2025

The existing detection for export doesn't appear to be robust. For some reason for my export meter (I guess related to the ongoing saga I've been having with Octopus to set it up), both the smartImportElectricityMeter and smartExportElectricityMeter fields in the GraphQL response are None, which means the export meter gets detected as an import meter instead.

Fortunately, the meterPoint GraphQL object includes a "direction" enum value which indicates whether meters within it are import or export meters.

This PR updates the query to fetch this direction field, and if present uses it to set whether an electricity meter is export. If the field is missing or none, it fails back to the old logic,

Fixes #1594

The meterPoint graphql object has a "direction" enum value which indicates whether meters within are import or export meters. Update the query to include this direction field and use it to set whether an electricity meter is export.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Export Meter shows as Import

1 participant