Do you have Zendure batteries? And are you charging your car at the same time? Not good… 😉

Zendure EV Guard

Protect your Zendure batteries while charging your electric car

Compatible with Zendure SolarFlow 2400 AC • Shelly Pro 3EM • Smappee • Windows, Linux, macOS

Do you have Zendure batteries and an electric car?

You know the problem: when your car is plugged into the wallbox, it draws everything. Your Zendure batteries drain at full speed, cycles accumulate, and the lifespan of your precious cells melts away.

If your car is a company vehicle and the electricity is paid for by your employer, it is a shame to drain your batteries to recharge it, only to have nothing left in the evening for your home's self-consumption.

Another scenario: even if it is not a company car, you may simply want to prevent your batteries from discharging while charging, so you can fully benefit from the electricity produced by your solar panels in bright sunshine, without drawing from your Zendure batteries.

Zendure EV Guard solves this problem automatically. As soon as your car's charging is detected, the program pauses your batteries. When charging is complete, it reactivates them. Simple, automatic, risk-free.

How does it work?

1. Detection

Your Shelly Pro 3EM (or Smappee) measures consumption. When power exceeds the threshold (e.g., 5000W), the program knows that your car is charging.

🔋

2. Protection

The Zendure batteries instantly switch to OFF mode. They no longer discharge, and your cycles are preserved.

3. Resumption

Charging complete? The program automatically reactivates your batteries with your original settings. No manual intervention.

🔒 100% safe for your batteries

Zendure EV Guard uses exclusively the local HTTP API of your Zendure hub. It modifies only a single parameter: minSoc (minimum charge level). To pause, it sets minSoc to 100%, which prevents any discharge. To resume, it restores your usual value (for example, 10%).

No modified firmware, no cloud access, no risk. It is exactly the same as if you changed the setting manually in the Zendure app, but automatically and at the right time.

Prerequisites

EquipmentDetails
Zendure SolarFlow 2400 ACHub with active local HTTP API (port 80)
Shelly Pro 3EM or Smappee1 requiredCurrent clamp (Shelly, real time) or Smappee energy monitor (cloud API, 5-minute intervals) to measure consumption
Wallbox / Charging stationAny charging station: detection is based on consumption, not on the charging station itself
PC, Server or NASWindows, Linux or macOS, the program runs in the background 24/7
 

Installation

1. Extract the archive

Extract the contents of the ZIP file into the directory of your choice, for example:

  • Windows : C:\ZendureEvGuard\
  • Linux : /home/ZendureEvGuard/
  • macOS : /Applications/ZendureEvGuard/

2. Execution permissions (Linux / macOS only)

On Linux and macOS, you must make the file executable before launching it:

chmod +x ZendureEvGuard
./ZendureEvGuard

3. Configure appsettings.json

Open the appsettings.json file located next to the executable and fill in your settings (see the section below).

4. Launch the program

# Windows
ZendureEvGuard.exe

# Linux / macOS
./ZendureEvGuard

The program displays the connection information at startup. Use P to pause manually, R to resume, and Ctrl+C twice to stop cleanly.

Linux Tip: To keep the program running continuously even after disconnection, install it as a systemd service. Here's how:

a) Create a dedicated user (optional but recommended):

sudo useradd -r -s /usr/sbin/nologin zendure
sudo chown -R zendure:zendure /home/ZendureEvGuard

b) Create the service file:

sudo nano /etc/systemd/system/zendure-evguard.service

Paste the following content:

[Unit]
Description=ZendureEvGuard - EV Charging Battery Protection Daemon
After=network.target

[Service]
Type=simple
WorkingDirectory=/home/ZendureEvGuard
ExecStart=/home/ZendureEvGuard/ZendureEvGuard
Restart=on-failure
RestartSec=10
SyslogIdentifier=zendure-evguard
User=zendure
Environment=DOTNET_ENVIRONMENT=Production

[Install]
WantedBy=multi-user.target

c) Enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable zendure-evguard
sudo systemctl start zendure-evguard

d) Useful commands:

# Voir le statut
sudo systemctl status zendure-evguard

# Voir les logs en temps reel
sudo journalctl -u zendure-evguard -f

# Redemarrer apres une mise a jour
sudo systemctl restart zendure-evguard

# Arreter le service
sudo systemctl stop zendure-evguard

Configuration: appsettings.json

Here are all the settings you can configure. The Shelly and ZendureDevice sections are required.

⚡ Shelly required

Configuration of your Shelly Pro 3EM. This is the sensor that measures your home's electricity consumption.

ParameterDescriptionExample
EnabledEnable Shelly as the measurement sourcetrue
HostIP address of your Shelly Pro 3EM on your local network"192.168.1.50"
UseDigestAuthEnable if you have protected your Shelly with a passwordfalse
UsernameUsername (if authentication is enabled)"admin"
PasswordPassword (if authentication is enabled)"monmotdepasse"

🔌 Smappee charging station optional

The Smappee energy station can be used in two ways:

  • As an EV detection source (alternative to Shelly): if Shelly is disabled, Smappee becomes the power measurement source for detecting EV charging. Detection is performed via the Smappee cloud API (5-minute blocks, less responsive than Shelly in real time).
  • In parallel with Shelly: if Shelly is active as the detection source, Smappee can still be enabled to continuously display consumption information (solar, home, grid) and information about your Smappee EV Wall charging station (charging power, status, etc.) in the logs.
ParameterDescriptionExample
EnabledEnable Smappee (detection source if Shelly is disabled, or display consumption/EV charger information in parallel)false
ClientIdClient ID of your Smappee application (API v3)"votre-client-id"
ClientSecretClient Secret of your Smappee application"votre-client-secret"
UsernameUsername of your Smappee account"user@email.com"
PasswordPassword for your Smappee account"motdepasse"
ServiceLocationIdID of your Smappee location (visible in the Smappee dashboard; this is not the serial number)"190802"
PollingIntervalSecondsSmappee API polling frequency30

🔋 Zendure Battery required

Configuration of your Zendure SolarFlow 2400 AC hub or others. The IP address can be found in the Zendure app.

ParameterDescriptionExample
HostIP address of your Zendure hub on the local network"192.168.1.127"
PortLocal API HTTP port (80 by default)80
DefaultOutputLimitMaximum output power in watts to restore after EV charging2400
DefaultMinSocDischarge floor to restore after charging: the level below which your batteries will no longer discharge (the value is ×10: 100 = 10%, 200 = 20%). This is not the maximum charge level.100
TimeoutSecondsTimeout for requests to the hub10

💡 Understanding DefaultMinSoc

This parameter defines the discharge floor of your batteries: the level below which the hub will no longer allow them to discharge. The value is multiplied by 10 in the Zendure API:

  • 100 = the batteries can drop as low as 10%
  • 200 = the batteries can drop as low as 20%
  • 500 = the batteries stop at 50%, and half of your capacity is no longer usable

Do not confuse this with the charge ceiling. The level at which your batteries stop charging is socSet, another setting, the one you see in the Zendure app. Setting 950 here therefore does not mean "charge up to 95%" but "never go below 95%": your batteries become unusable. Since version 1.3.0, the program refuses to start with a value outside the range of 1 to 999 and warns you above 500.

The choice is yours! The lower the value, the more you use your batteries; the higher it is, the more you preserve the cells, at the cost of available capacity. Most users choose between 100 (10%) and 200 (20%).

🚗 EvDetection

Settings for detecting your electric vehicle's charging. The algorithm uses hysteresis: several consecutive readings above the threshold are required to confirm charging, and several readings below it to confirm that charging has stopped.

ParameterDescriptionDefault
PowerThresholdWattsPower threshold (in watts) above which the program considers that a car is charging. Adjust it to your wallbox.5000
ConfirmationReadingsNumber of consecutive readings above the threshold required to confirm the start of charging2
ReleaseReadingsNumber of consecutive readings below the threshold required to confirm the end of charging (24 = ~2 minutes at 5s/reading)24
PollingIntervalSecondsMeasurement frequency in seconds5
PauseOnSourceUnreachableMinutesNew in 1.3.0. Duration for which the meter can remain unreachable before the batteries are paused as a precaution: while blind, the program can no longer see your car plug in. The pause is lifted as soon as the first valid measurement is received. Set to 0 to disable this safeguard.3

📬 Notification optional

Receive emails when your batteries pause, resume, or in case of an error. Configure your SMTP server.

ParameterDescriptionDefault
EnabledEnable email notificationsfalse
SmtpHostSMTP server (e.g.: smtp.gmail.com)""
SmtpPortSMTP port587
UseSslUse TLS/SSLtrue
Username / PasswordSMTP credentials""
FromAddressSender's email address""
ToAddressRecipient(s), separated by ; for multiple recipients""
RateLimitMinutesMinimum interval between two alerts (anti-spam)15

📴 Pushover optional

Push notifications on your phone via Pushover. Create an application on pushover.net to obtain your API Token.

ParameterDescription
EnabledEnable Pushover (true / false)
ApiTokenAPI Token of your Pushover application
UserKeyYour Pushover user key
RateLimitMinutesMinimum interval between alerts (default: 15)

💬 Telegram optional

Notifications via a Telegram bot. Create a bot with @BotFather and retrieve your Chat ID.

ParameterDescription
EnabledEnable Telegram (true / false)
BotsList of bots. Each one has its Name, its BotToken, and its list of ChatIds. This makes it possible to notify different people in different groups
RateLimitMinutesMinimum interval between alerts (default: 15)

Since 1.2.0, you can notify several groups at once: two people via a first bot, and three others via a second. Each sending operation is isolated; an unreachable recipient no longer prevents the others from receiving the message.

"Telegram": {
  "Enabled": true,
  "RateLimitMinutes": 15,
  "Bots": [
    {
      "Name": "Famille",
      "BotToken": "123456:AAExxxxxxxxxxxxxxxxxxxx",
      "ChatIds": [ "11111111", "22222222" ]
    },
    {
      "Name": "Voisins",
      "BotToken": "789012:BBEyyyyyyyyyyyyyyyyyyyy",
      "ChatIds": [ "33333333", "44444444", "55555555" ]
    }
  ]
}

The old format, with a single BotToken and ChatId values separated by semicolons, continues to work. If you do not change anything in your configuration, your notifications will continue exactly as before.

📈 Monitoring optional

ParameterDescriptionDefault
HealthCheckIntervalSecondsFrequency for checking device connectivity30
LogStatusIntervalSecondsFrequency for logging the complete status in the log files300

🔄 Update optional

Since 1.2.0, the program no longer updates itself. It checks once an hour whether a newer version is available and simply notifies you: a reminder in the logs every hour until you have installed the new version, and a single message on the channels you have configured, with the direct download link.

Replacing the binary of a service that protects your batteries while it is running is the riskiest operation in the product. It is better for you to decide when to do it. The old keys AutoUpdateEnabled and CheckIntervalHours are no longer read: you can leave them in your file; they are ignored.

ParameterDescriptionDefault
CheckEnabledCheck every hour whether a newer version existstrue
NotifyOnNewVersionSend a message to your notification channels upon the first detection of a version. Only once per version, never repeatedtrue

🔑 License after the trial

After the 30-day trial period, add your secret key to activate the PRO license. Your key can be found in your account at top right > "My Account". The license renews automatically in the background.

ParameterDescriptionExample
SecretKeyYour unique secret key (GUID) from your digital3d.com account. Leave empty to use trial mode.d79d24cc-eb02-48d7-94f8-xxxxxxxxxxxx

Minimal configuration example

Here is a ready-to-use example. Simply replace the IP addresses with those of your devices:

{
  "Shelly": {
    "Enabled": true,
    "Host": "192.168.1.50"
  },
  "ZendureDevice": {
    "Host": "192.168.1.127",
    "Port": 80,
    "DefaultOutputLimit": 2400,
    "DefaultMinSoc": 100
  },
  "EvDetection": {
    "PowerThresholdWatts": 5000
  },
  "Subscription": {
    "SecretKey": "d79d24cc-eb02-48d7-94f8-xxxxxxxxxxxx"
  }
}

With this configuration, the program monitors your Shelly, detects any consumption above 5000W (for example), and restores your batteries with a minimum of 10% (100 ÷ 10) and a maximum output of 2400W. The Subscription section is empty by default: the program operates in trial mode for 30 days. To activate the PRO license, add your secret key from your account in the top right.

Free Trial & Subscription

🎉 30-day free trial, no commitment!

Download Zendure EV Guard and try it for 30 full days, without paying anything and with no feature limitations. You will have access to 100% of the features to make sure that the program perfectly suits your setup.

At the end of the 30 days, a Digital3D subscription is required to continue using the program. A single subscription gives you access to all Digital3D applications (CompactForIA, AutoMouseMove, Zendure EV Guard, etc.).

🔑 How to activate your license

  1. Subscribe to a plan on "One for All"
  2. Log in to your account at digital3d.com and copy your secret key (a unique identifier in GUID format, for example: f89f26cc-eb03-48d7-94f8-xxxxxxxxxxxx)
  3. Open the appsettings.json file and add your key in the Subscription section:
    "Subscription": {
      "SecretKey": "votre-clef-secrete-guid"
    }
  4. Restart the program: the PRO license is activated automatically and renews without any action on your part.

Ready to protect your batteries?

Download for free, configure it in 5 minutes, and sleep soundly.

One for All ” subscription: a single subscription for all Digital3D applications.

Download — Version 1.3.0

Version history
1.3.0 8/6/2026Current
- Le plancher de décharge par défaut (DefaultMinSoc) passe de 950 à 100 : à 950, les batteries n'avaient plus le droit de descendre sous 95%, donc plus rien à donner - Au démarrage, une valeur de DefaultMinSoc hors de 1 à 999 est refusée, et une valeur au-dessus de 500 déclenche un avertissement - Nouvelle clé EvDetection.PauseOnSourceUnreachableMinutes (3 par défaut) : si le compteur reste injoignable plus longtemps, les batteries sont mises en pause par précaution, jusqu'à la première mesure valide - La clé Smappee.EvThresholdWatts n'existe plus, elle n'était lue nulle part - L'état d'avant-pause est enregistré sur disque : un redémarrage pendant une pause ne perd plus les valeurs à restaurer - Correction : la notification « batteries pleines » se basait sur le plancher de décharge au lieu du plafond de charge du hub - Correction : plus de fausse restauration au démarrage en pleine journée, qui envoyait un e-mail et un message pour rien - Correction : après une reprise, la vérification automatique surveille la valeur réellement envoyée à l'appareil
1.2.0 8/5/2026
- The program no longer updates itself automatically: it checks every hour and notifies you, only once per version. - Hourly reminders in the logs as long as the new version is not installed, with the download link. - New keys in the Update section: CheckEnabled and NotifyOnNewVersion. - The old keys AutoUpdateEnabled and CheckIntervalHours are no longer read, they are simply ignored. - Telegram: multiple bots, each with its own list of recipients, via the new Bots list. - The old Telegram configuration continues to work as is. - An unreachable recipient no longer prevents others from receiving the message. - Fix: a value too large in the old check interval could stop the service.
1.1.0 4/1/2026
- Bug fixes
Join the conversation

You need an account to comment on this article. Creating one is free and takes under a minute.

  • The XMLTV file, free to download every day
  • Comment on articles and reply to other readers
  • Get an e-mail when an article you follow is updated

No comments yet.

Une erreur s'est produite. Cette application peut ne plus répondre jusqu'à ce qu'elle soit rechargée.Veuillez contacter l'auteur. Reload 🗙