New API specification for V3 and V4 go-eCharger
active 2023-08-19 → 2026-08-12 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1090 days from 2023-08-19 to 2026-08-12. Pushes: 59 total, peak 8 in a day. Pull requests: 14 total, peak 2 in a day. Issues: 126 total, peak 4 in a day. Comments: 387 total, peak 11 in a day. Stars: 52 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| erxbout | 101 | 1 | 0 | 72 |
| 0xFEEDC0DE64 | 63 | 15 | 6 | 39 |
| georggruber-goe | 42 | 42 | 0 | 0 |
| schinagl | 29 | 0 | 3 | 23 |
| chk2902 | 22 | 0 | 0 | 16 |
| Twiederh | 13 | 0 | 0 | 12 |
| mincequi | 11 | 0 | 0 | 5 |
| marq24 | 10 | 0 | 2 | 5 |
| tmcrash | 8 | 0 | 0 | 8 |
| fredlcore | 8 | 0 | 0 | 7 |
| juergen852 | 8 | 0 | 0 | 6 |
| powo01 | 8 | 0 | 0 | 8 |
| wrzlbrmft1 | 7 | 0 | 0 | 4 |
| mleck28 | 7 | 0 | 0 | 5 |
| CommanderRedYT | 7 | 0 | 0 | 7 |
| karliwalti | 6 | 0 | 0 | 5 |
| mmick08 | 6 | 0 | 0 | 5 |
| povlhp | 6 | 0 | 0 | 5 |
| rainer4 | 6 | 0 | 0 | 5 |
| peterpoetzi | 5 | 0 | 1 | 3 |
Recent activity
Latest issues, pull requests and releases
- Issue#319nilshoell2026-04-06 20:52Rounding Mode parameter (frm) is R/W, not readonly as mentioned in the docs
- Issue#315Rumbelstilzchen2026-03-31 21:39after restart of mqtt broker, pv data cannot be set
- Issue#310Kaktusd2026-03-10 12:24Modbus 40300 (299 - AMPERE_VOLATILE) setzt auch 40301 (300 - AMPERE_EEPROM) -- Zerstoerungsgefahr?
- Issue comment#309chk29022026-03-09 12:03go-E Gemini stuck at 6A
- Issue comment#92fre42422026-03-06 13:46Feature request: AMP stufenlos regeln?
- Issue#307DoWenzl942026-02-21 00:02„dyn“ lässt sich nicht per mqqt setzten
- Issue comment#3064vplacek2026-02-15 11:38Beta Firmware 60.3, Winsock API: "frc" does not work
- Issue comment#200reinsch822026-02-10 11:29Incorrect Awattar marketprice for smartCONTROL tariff from smartENERGY (Energie Steiermark)
- Issue comment#303marq242026-02-06 13:53Set sch_week via http api?
- Issue#301gorootde2026-02-02 21:01Laden freischalten / sperren per API
- Issue#299gsieben2026-01-30 15:39The API function stops working after a while
- Issue#276erxbout2025-12-30 20:47some API Keys not working via MQTT
- Issue comment#294erxbout2025-12-28 19:49AxiosError: Request failed with status code 404
- Issue comment#294Klaus-Lucas2025-12-26 21:18AxiosError: Request failed with status code 404
- Issue comment#294erxbout2025-12-26 20:31AxiosError: Request failed with status code 404
- Issue#295rosch992025-12-19 12:44new "modelStatus" 39
- Issue comment#294Klaus-Lucas2025-12-15 13:51AxiosError: Request failed with status code 404
- Issue#294Klaus-Lucas2025-12-14 19:08AxiosError: Request failed with status code 404
- Issue comment#293erxbout2025-12-08 10:1515 minute flexible tariffs do not work correctly with firmware lower than 60.0 (as designed)
- Issue comment#293schorfi2025-12-08 10:02Flexible energy traiff: Eco mode and price limit does not behave correctly, doesnt charge or does not correctly predict charge periods
- Issue comment#292sr2582025-12-08 05:28power_total kann nicht in Home Assistant für Stromverbrauchsanzeige verwendet werden
- Issue#249erxbout2025-12-08 00:44SetChargingProfile did not work
- Issue#292erxbout2025-12-08 00:39power_total kann nicht in Home Assistant für Stromverbrauchsanzeige verwendet werden
- Issue comment#293erxbout2025-12-08 00:38Flexible energy traiff: Eco mode and price limit does not behave correctly, doesnt charge or does not correctly predict charge periods
- Issue comment#287sballieu2025-12-07 17:19API access after FW 60 and factory reset
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 52 stars here means stars gained during the window, not the repo's star count.