How does it work?

Prerequisites

Installation

1. Unzip 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).

Or, much simpler, let the wizard do it. It asks the questions one by one, shows the current value in brackets (Enter keeps the value), tests each device as it goes and only touches the settings you change:

# Windows
ZendureEvGuard.exe --setup

# Linux / macOS
./ZendureEvGuard --setup

The required hardware is announced right away: a meter and Zendure batteries are required, a Smappee charging station is optional. For the meter, the assistant simply asks which one: 1 for the Shelly Pro 3EM (the default choice, Enter is enough), 2 for your own sensor. Threshold calibration is ideally done during a real car charging session: it measures the house with and without the vehicle and suggests the value. No car available? We skip the step and keep the current threshold. At the end, it offers to restart the service so that it applies the new settings, or gives the exact command to type if the service is not installed yet.

A doubt later? The diagnostic reads everything again without changing anything:

./ZendureEvGuard --doctor
./ZendureEvGuard --doctor --notify   # envoie aussi un message de test

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
sudo sh install-linux.sh

# macOS
sudo sh install-macos.sh

# Windows (PowerShell en tant qu'administrateur)
powershell -ExecutionPolicy Bypass -File .\install-windows.ps1

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

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

[Install]
WantedBy=multi-user.target

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

# 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

Configuration: appsettings.json

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

Messages

The language of everything you read: emails, Pushover, Telegram, end-of-charge reports. Technical logs remain in English, so that an error message can still be searched for.

Pay attention to where you put it: this key goes under the Messages section, never at the root of the file. On Linux, a Language key placed at the root is overridden by the system's LANGUAGE environment variable, and your messages switch back to English without warning.

"Messages": {
  "Language": "fr"
}

Shelly required

Configuration of your Shelly Pro 3EM. It's the sensor that measures your home's electricity consumption. Don't have a Shelly? See "Your own sensor" just below.

Your own sensor instead of the Shelly

Do you already have a meter that measures your connection, in Home Assistant, Jeedom, Tasmota, ESPHome or another Shelly? No need to buy a Shelly Pro 3EM: ZendureEvGuard will read one number from a URL on your local network that responds in JSON, every 5 seconds. With a Shelly Pro 3EM, simply ignore this section: without it, everything works as before.

"CustomMeter": {
  "Enabled": true,
  "Url": "http://192.168.1.50:8123/api/states/sensor.puissance_reseau",
  "ValuePath": "state",
  "Unit": "W",
  "InvertSign": false,
  "Authentication": "Bearer",
  "BearerToken": "votre-jeton-longue-duree"
}

The only slightly technical setting is ValuePath : the path to the number in the response. A few examples that work :

• Home Assistant (/api/states/sensor.xxx, long-lived token in Bearer) : state
• Shelly Gen1 EM : emeters[0].power
• Shelly Gen2 (/rpc/EM.GetStatus?id=0) : total_act_power
• Tasmota (/cm?cmnd=Status%208) : StatusSNS.ENERGY.Power
• ESPHome (/sensor/xxx) : value
• Jeedom (jeeApi.php, which returns the number alone) : leave blank

Unit is W or kW, InvertSign is used if your sensor counts solar export as positive, and Authentication accepts None, Basic (with Username and Password) or Bearer. --setup asks all these questions and performs a test reading that displays the raw value and the watts, for example lecture 1500 W (valeur lue : 1.5). Above 60 kW, it warns you: it is almost always confusion between W and kW.

Watch out for your sensor choice : you need the grid power, at the house meter, positive when you draw power and negative when you export. Not a « house consumption » sensor, which is already counting what the battery supplies and would make it look like a charge. And the safety remains the same as for the Shelly: a sensor that does not respond, takes more than 4 seconds or returns unavailable triggers the precautionary pause. The URL, password and token never appear in the logs.

Smappee charging station optional

The Smappee energy station can be used in two ways :

• As an EV detection source (alternative to the Shelly) : if the Shelly is disabled, Smappee becomes the power measurement source for detecting EV charging. Detection is done via the Smappee cloud API (5-minute blocks, less responsive than the Shelly in real time).
• In parallel with the Shelly : if the Shelly is active as the detection source, Smappee can still be activated to continuously display consumption information (solar, house, grid) and information about your Smappee EV Wall charging station (charging power, status, etc.) in the logs.

Battery Zendure required

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

EvDetection

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

Energy

At the end of each charge, the program tells you how many kWh have been used. Give it the price of your kWh and it adds the amount. It is indicative, not an invoice: nobody measures the charging station itself, and the price is fixed while yours may not be.

The use case I have in mind: several cars plug in at your place, and each one needs to know what it has consumed.

The report gives figures for two amounts of energy. The one measured at the meter, which is a fact. And the vehicle's estimated share, which subtracts the house's usual consumption: an estimate, and a maximum when your panels were exporting at the time you plugged in.

Charge terminee : 1h03 | 11,30 kWh au compteur (3,16 EUR) |
~11,30 kWh pour le vehicule (3,16 EUR) | pointe 14627 W | moyenne 11169 W

Notification optional

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

📴 Pushover optional

Push notifications on your phone via Pushover. Create an application on pushover.net to get your API Token. The simplest way: --setup asks you for the key and token, then sends a test message before activating the channel.

💬 Telegram optional

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

You can notify several groups at once: two people via a first bot, three others via a second. Each send 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" ]
    }
  ]
}

And commands. A bot can also receive your orders. /status gives the battery and counter status, /pause and /resume do exactly what the P and R keys do, and /license <votre clé> activates a license (the bot immediately deletes the message containing the key). This is disabled by default and is enabled bot by bot:

{
  "Name": "Commandes",
  "BotToken": "345678:CCFzzzzzzzzzzzzzzzzzzzz",
  "ChatIds": [ "11111111" ],
  "CommandsEnabled": true
}

Only the conversations listed in ChatIds are obeyed, a command more than 5 minutes old is ignored, and /resume is refused during charging (the battery would be paused again on the next cycle). Personally, I reserve one bot for these commands and don't put it in any group: anyone who can write in the conversation can pause your battery.

For a single bot, the short form works too: one BotToken and ChatIds separated by semicolons.

📈 Monitoring optional

Update optional

License after 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.

You can also send it to your Telegram bot, without touching the file: /license <votre clé>. The bot deletes the message, activates the license and replies with the result (activated until, refused, account suspended). Commands must be enabled on this bot.

Minimal configuration example

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

{
  "Messages": {
    "Language": "fr"
  },
  "Energy": {
    "PricePerKwhCents": 28
  },
  "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 works in trial mode for 30 days. To activate the PRO license, add your secret key from your account at the top right.

Free trial & Subscription