Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARP1 API: wrong /evse/automation_current? #67

Open
Alestrix opened this issue Jan 25, 2025 · 1 comment
Open

WARP1 API: wrong /evse/automation_current? #67

Alestrix opened this issue Jan 25, 2025 · 1 comment

Comments

@Alestrix
Copy link

Alestrix commented Jan 25, 2025

Hi,

I have an automation coming from my Shelly EM3 that limits the WARP's current if it detects overpower on one of the phases of the house's point of delivery.
When it triggers, one can see it in the WARP's GUI:
Image

It can also be seen at slot 14 via the API:

$ curl --silent http://wallbox/evse/slots|jq '.[14]'
{
  "max_current": 8000,
  "active": true,
  "clear_on_disconnect": false
}

However, the automation_current is still reported to be 32 amps:

$ curl --silent http://wallbox/evse/automation_current|jq
{
  "current": 32000
}

So either /evse/automation_current is not updated or it refers to some other automation (according to the reference it's "Der von der Automatisierung erlaubte Ladestrom.").

I'll work around it by using slot[14] (will that number 14 remain the same in future firmware versions?), but this still should be fixed.

WARP 1, Version 2.6.6+675aea10 (also tested with 2.6.1 showing the same behavior)

@rtrbt
Copy link
Member

rtrbt commented Jan 27, 2025

So either /evse/automation_current is not updated

Exactly that. Should be fixed with this firmware (you have to extract the zip first, Github does not allow to upload bin files):

warp_firmware-NIGHTLY_2_6_6_679748cd_c4005e8a6f81e55__merged.bin.zip

Thanks for the bug report!

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

No branches or pull requests

2 participants