Quantify Issues

Recent GitHub Issues Activity

_{Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.}

Quantify commits

Quantified Commit Activity Over 30 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
andig		21	59/44/7	176	255	63210
Michael Geers		9	21/20/2	40	94	6122
Weblate (bot)		1	5/4/1	4	17	1431
premultiply		4	23/21/1	36	38	1148
wobu		1	1/1/0	1	4	399
kscholty		1	0/0/0	1	5	288
Andreas Linde		2	13/11/1	11	11	168
Filipe Lima		1	0/0/0	1	3	105
Herbert23		1	0/1/0	1	2	50
xerion3800		1	1/1/0	1	6	47
oscarminus		1	1/1/0	1	1	25
Rene Nulsch		2	3/3/0	3	3	16
Jorge		1	1/1/0	1	1	14
None (blenni)		1	1/1/0	1	1	12
mdkeil		1	1/1/0	1	1	12
Žiga Deisinger		1	0/0/0	1	1	10
dependabot[bot]		1	2/1/1	1	2	10
Michael Heß		1	2/2/0	2	2	9
Joonas Kuorilehto		1	1/1/0	1	1	7
deadrabbit87		1	3/1/2	1	1	6
RTTTC		2	2/1/1	2	2	5
carygravel		1	1/1/0	1	1	5
achgut		1	1/1/0	1	1	4
Stefan		1	1/1/0	1	1	4
Sven Giermann		1	2/1/0	1	1	3
Tom Jason Schwanke (tomjschwanke)		1	2/1/0	1	1	2
ftonellotto		1	0/0/0	1	1	1
Hans Schulz (schulzh)		0	1/0/0	0	0	0
None (MarkusGH)		0	1/0/1	0	0	0
None (madmat17)		0	1/0/1	0	0	0
None (benesolar)		0	2/0/2	0	0	0
Dominik Niakamal (dniakamal)		0	1/0/1	0	0	0
None (luejoshua)		0	1/0/0	0	0	0
Ingo (iseeberg79)		0	1/0/0	0	0	0
None (ramikeller)		0	1/0/1	0	0	0

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The recent activity in the evcc-io/evcc GitHub repository indicates a significant uptick in issues, particularly following the release of version 0.130.6. There are currently 66 open issues, with many users reporting problems related to charger connectivity, configuration errors, and unexpected behavior after updates. A recurring theme is the impact of software updates on charger functionality, particularly with OCPP connections and specific wallbox models, leading to user frustration.

Notably, several issues highlight critical failures such as chargers not starting, incorrect power readings, and persistent error messages that hinder normal operation. The community appears to be actively engaged in troubleshooting these problems, but the volume of unresolved issues suggests that the latest updates may have introduced instability or compatibility problems.

Issue Details

Here are some of the most recently created and updated issues:

1. Issue #15774: Charging doesn't start while there is a lot of PV surplus

   • Priority: Question
   • Status: Open
   • Created: 0 days ago
   • Updated: N/A
   • Details: User reports that charging does not commence despite sufficient solar generation, indicating potential misconfigurations or bugs in the logic handling PV surplus.

2. Issue #15772: smart #1 Auto-Detection, SoC, km-Stand u.a. funktionieren bei mir nicht

   • Priority: Devices
   • Status: Open
   • Created: 0 days ago
   • Updated: N/A
   • Details: Issues with vehicle detection and state of charge (SoC) reporting for a smart #1 vehicle.

3. Issue #15768: Project EV

   • Priority: Question
   • Status: Open
   • Created: 0 days ago
   • Updated: N/A
   • Details: User experiences errors after upgrading to version 0.130.# with an OCPP charger.

4. Issue #15766: OpenWB - Improve Documentation

   • Priority: Devices
   • Status: Open
   • Created: 0 days ago
   • Updated: N/A
   • Details: User requests better documentation for integrating OpenWB wallboxes with EVCC.

5. Issue #15752: OCPP: evcc unable to charge wants to unplug replug car always (EN+ firmware)

   • Priority: Question
   • Status: Open
   • Created: 1 day ago
   • Updated: 1 day ago
   • Details: User reports persistent issues with OCPP charger requiring manual intervention to initiate charging.

6. Issue #15745: Elvi EVBox: Cable not released after charging is complete (after upgrade to 0.130.6)

   • Priority: Question
   • Status: Open
   • Created: 1 day ago
   • Updated: 1 day ago
   • Details: User indicates that the cable remains locked post-charging, requiring a power cycle to release it.

7. Issue #15735: Kein recovery nach mqtt-Server-Ausfall

   • Priority: Bug
   • Status: Open
   • Created: 1 day ago
   • Updated: N/A
   • Details: Reports that EVCC fails to recover from MQTT server outages effectively.

8. Issue #15697: Charger Delta AC MAX Basic (Modbus) wrong charger status

   • Priority: Devices, Backlog
   • Status: Open
   • Created: 2 days ago
   • Updated: 1 day ago
   • Details: Incorrect charging status reported by Delta AC Max Basic charger; user suggests a solution involving register differentiation.

9. Issue #15688: eebus works on 0.126.1 but does not on 0.130.4

   • Priority: Question
   • Status: Open
   • Created: 3 days ago
   • Updated: N/A
   • Details: User reports loss of EEBUS functionality after upgrading from an earlier version.

10. Issue #15677: OCPP: Mennekes Smart Charging Station seit 0.130.0 Fehlerhaft

    • Priority: Enhancement
    • Status: Open
    • Created: 3 days ago - Updated: N/A - Details: User indicates failure to start charging after updating to version 0.130.x.

Summary

The analysis reveals a pattern of user-reported issues primarily linked to recent updates and their impact on charger functionality and connectivity within the evcc ecosystem. The community's active engagement suggests a collaborative effort to diagnose and resolve these challenges, though the sheer volume of open issues indicates a pressing need for stability improvements in future releases.

Report On: Fetch pull requests

Overview

The evcc repository has a total of 26 open pull requests (PRs), with a mix of enhancements, bug fixes, and device support updates. The recent activity indicates a strong focus on improving the EEBUS protocol integration, enhancing OCPP functionalities, and addressing various device compatibility issues.

Summary of Pull Requests

1. PR #15778: EEBUS: Monitor measurements after limit change

   • State: Open
   • Significance: Introduces monitoring for EEBUS wallboxes to ensure measurements are provided within a specified time after a limit change. This enhances user feedback regarding non-functional metering.
   • Notable: Immediate response to a critical functionality issue.

2. PR #15773: Ocpp: don't use stacklevel for default profile

   • State: Open
   • Significance: Fixes an issue related to the stackLevel parameter in OCPP charging profiles, aligning with specifications.
   • Notable: Directly addresses an existing issue (#15493).

3. PR #15762: Ocpp: provide better support for multiple connectors

   • State: Open
   • Significance: Refactors the setup process for charge points to reduce startup errors by moving initialization logic.
   • Notable: Involves extensive review comments indicating complexity and potential improvements.

4. PR #15723: Translations update from Hosted Weblate

   • State: Open
   • Significance: Updates translations for multiple languages, ensuring broader accessibility of the software.
   • Notable: High completion rate across languages.

5. PR #15709: Kostal Plenticore: add grid charging

   • State: Open
   • Significance: Adds functionality for grid charging in the Kostal Plenticore system, enhancing its operational capabilities.
   • Notable: Discussion around register management indicates careful consideration of existing functionalities.

6. PR #15680: Add rudimentary battery controls to Growatt Hybrid

   • State: Open
   • Significance: Introduces basic battery control features for the Growatt hybrid inverter, expanding its usability.
   • Notable: Detailed explanation of operational modes adds clarity to implementation.

7. PR #15660: Ocpp: move get/set charging profile to connector

   • State: Open
   • Significance: Refactors code to improve the handling of charging profiles within connectors, aiming for better organization and efficiency.
   • Notable: Draft status indicates ongoing work and potential complexity.

8. PR #15631: Loadpoint: ignore charger out of sync if vehicle is disconnected

   • State: Open
   • Significance: Adjusts logic for handling charger synchronization based on vehicle connection status, improving error handling.
   • Notable: Addresses a specific logical inconsistency in the codebase.

9. PR #15615: Devices: use EVCC_SEQUENTIAL to serialize device creation

   • State: Open
   • Significance: Implements sequential initialization for devices, which may enhance stability during startup processes.

10. PR #15565: Sungrow-Hybrid: extend template by phase currents to support load management

    • State: Open
    • Significance: Enhances the Sungrow hybrid template to include phase current readings, crucial for load management applications.

11-26. Additional PRs focus on various enhancements, bug fixes, and updates related to device compatibility and performance improvements.

Analysis of Pull Requests

The recent pull requests in the evcc repository showcase several key themes and trends that reflect both ongoing development efforts and community engagement:

Focus on EEBUS and OCPP Protocols

A significant number of open PRs are dedicated to enhancing support for EEBUS and OCPP protocols, indicating a concerted effort to improve interoperability with various EV chargers and systems. For instance, PRs like #15778 and #15773 directly address critical functionalities within these protocols, suggesting that maintaining compliance with evolving standards is a priority for the project.

Device Compatibility Enhancements

Many PRs aim to improve compatibility with specific devices or families of devices (e.g., Kostal Plenticore in PR #15709 and Growatt Hybrid in PR #15680). This reflects the project's commitment to ensuring that users can effectively integrate their existing hardware with the EVCC system.

Community Engagement and Review Process

The detailed comments and discussions surrounding many of these PRs indicate an active community engaged in collaborative development. For example, PR #15762 features extensive review comments that explore various aspects of the implementation, showcasing a thorough vetting process before merging changes into the main branch.

Anomalies and Challenges

There are notable challenges reflected in some PR discussions, particularly around complex refactoring efforts (e.g., PR #15762) and device-specific issues (e.g., handling edge cases in PR #15709). These discussions highlight potential areas where further clarification or documentation may be needed to assist contributors in navigating complex codebases or device behaviors.

Lack of Merged Activity

While there is a healthy number of open PRs, it is essential to monitor the merging activity closely as well. The repository has seen numerous merges recently; however, some older PRs remain unmerged or unresolved (e.g., PR #15593). This could indicate bottlenecks in review processes or prioritization challenges within the team.

Conclusion

Overall, the current state of pull requests within the evcc repository reflects a dynamic development environment focused on enhancing protocol support, improving device compatibility, and fostering community collaboration. Continued attention to resolving open issues and streamlining the merging process will be crucial as the project evolves further in response to user needs and technological advancements in electric vehicle infrastructure.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

1. Andreas Linde (DerAndereAndi)

   • Recent contributions include:
   • Improved EEBUS support for Elli Gen 1, focusing on IPv6 connections and meter configurations.
   • Added optional IP address support for EEBUS devices.
   • Fixed crashes related to PMCC 1 phase setup charging for Taycan.
   • Worked on translations and updates for various templates.
   • Collaborated with others on EEBUS improvements and translations.

2. Michael Geers (naltatis)

   • Recent activities include:
   • Upgraded npm dependencies and node versions.
   • Stabilized flaky Playwright tests.
   • Added features to the Savings UI and improved logging in various components.
   • Engaged in multiple PRs related to UI improvements and dependency management.

3. Andig

   • Major contributor with numerous recent commits focusing on:
   • Fixes and enhancements across multiple components, particularly in OCPP handling, charger configurations, and logging improvements.
   • Reverted several previous changes indicating ongoing refinements in code stability.
   • Active in managing translations and improving compatibility with various chargers and meters.
   • Collaborated extensively with other team members on various features.

4. Premultiply

   • Focused on:
   • Enhancements to OCPP functionalities, including error handling and measurement behavior.
   • Refactoring templates for better organization and clarity.
   • Worked alongside Andreas Linde on EEBUS improvements.

5. Weblate (bot)

   • Automated translations updates across multiple languages, ensuring the project remains accessible to a wider audience.

6. RTTTC

   • Contributed minor updates primarily focused on translations.

7. Other Contributors (e.g., Giermann, oscarminus, etc.)

   • Involved in smaller feature additions or bug fixes, primarily related to specific chargers or UI improvements.

Patterns and Themes

• Active Collaboration: The team exhibits strong collaboration, especially between Andreas Linde and Andig, who frequently work together on EEBUS-related features and improvements.
• Focus on Stability: A significant number of recent commits involve reverting previous changes, indicating a focus on stabilizing the codebase after identifying issues.
• Continuous Improvement: The team is actively enhancing existing features while also adding new functionalities, particularly in the areas of charger compatibility and user interface enhancements.
• Translation Efforts: There is a concerted effort to keep the project multilingual through automated translation updates by Weblate, which enhances accessibility for users across different regions.

Conclusions

The development team is highly active, with a clear focus on improving system stability, enhancing user experience through UI updates, and maintaining extensive compatibility with various EV chargers. The collaborative nature of the team fosters continuous improvement while addressing issues promptly through reverts and fixes. Overall, the project maintains a robust trajectory of growth and refinement in its functionalities.