Skip to content

Make public_settings and last_update_time nullable in API responses#10

Draft
Copilot wants to merge 2 commits intomasterfrom
copilot/fix-api-issues-march-2026
Draft

Make public_settings and last_update_time nullable in API responses#10
Copilot wants to merge 2 commits intomasterfrom
copilot/fix-api-issues-march-2026

Conversation

Copy link

Copilot AI commented Mar 24, 2026

The SolarEdge API (as of March 2026) now returns null for publicSettings in site details and lastUpdateTime in site overview responses, causing deserialization failures.

Changes

  • Details.public_settings: PublicSettingsOption<PublicSettings>
  • Overview.last_update_time: NaiveDateTime (with DateTimeSerde) → Option<NaiveDateTime> (with DateTimeSerdeOpt)
Original prompt

This section details on the original issue you should resolve

<issue_title>API Changes</issue_title>
<issue_description>In march 2026 solaredge changed the API. I found several issues.

https://knowledge-center.solaredge.com/sites/kc/files/se_monitoring_api.pdf

  • version_current() and maybe others were removed
  • public_settings in site details is null in my case (needs to be Option<>)

This is what I found so far. There are maybe more issues.

In the response from solaredge the peakPower is always 0.0 and the lastUpdateTime is null. I couldn't figure out why this is.

Kind regards</issue_description>

<agent_instructions>Take a look at the reported issues and adjust the API accordingly if necessary</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@twistedfall The missing functions were removed in the `v0.9.0`, I'll take a look at the other inconsistencies, thanks for the report!

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.

Copilot AI changed the title [WIP] Fix API changes due to SolarEdge update Make public_settings and last_update_time nullable in API responses Mar 24, 2026
Copilot AI requested a review from twistedfall March 24, 2026 07:27
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.

API Changes

2 participants