About
V2C Cloud connects Home Assistant to V2C Trydan chargers through the V2C cloud API and the charger's local HTTP interface. Frequent readings and controls use the local network, while configuration tasks go through the cloud, and polling runs every 30 seconds by default with an adjustable interval. It adds binary sensor, button, number, select, sensor and switch entities for charging state, power, energy, charge mode, dynamic power control, charger lock, RFID reader and OCPP. Actions cover charging timers, RFID card management, energy or time based charge stops, Wi-Fi settings, OCPP settings and personalised power profiles. A charger can also be set up from its local IP address alone, without a V2C account, and a manual IP address can be pinned per charger in the options. If the cloud rejects the API key or cannot be reached, a local setup keeps working and a repair notice appears.
Automatic summary of the README and code of samuelebistoletti/HomeAssistant-V2C-Cloud. Something wrong, or are you the maintainer and want your own text here? Get in touch
Supports
Uses the vendor's cloud Needs an internet connection and an account with the vendor.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.
Provides
- Switches
- Sensors
Setting it up
Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.
Connection type
- Connection type
V2C Cloud account
- API key
Also asked when signing in again and changing the connection.
Charger on the local network
- Charger IP address
After setup
- Connection type
- Local refresh interval (seconds)
- Set charger IP addresses manually
- IP address
Texts from the code of samuelebistoletti/HomeAssistant-V2C-Cloud.
Entities
- Binary sensorsConnection status
- ButtonsReboot charger, Trigger firmware update
- NumbersCurrent intensity, Minimum intensity, Maximum intensity, Contracted power, Light LED intensity
- SelectsInstallation type, Slave device, Language, Dynamic power mode, Charge mode
- SensorsDevice identifier, Firmware version, Charging state, Ready state, Charging power, Charging energy, Device error code, Charging time, House power, Photovoltaic power, Battery power, Timer status, and 11 more
- SwitchesDynamic mode, Pause dynamic control, Charger lock, Charging pause, Logo LED, RFID reader, OCPP, Timer
Actions
- Update Wi-Fi credentialsConfigure the Wi-Fi SSID and password for a charger.
- Configure charging timerSet start/end time and active week days for one of the device timers.
- Register RFID cardEnable card registration mode with the supplied label.
- Add RFID card manuallyRegister an RFID card by providing its UID and display name.
- Update RFID labelRename an existing RFID card.
- Delete RFID cardRemove a registered RFID card from the device.
- Set energy stopStop charging automatically after delivering a given amount of energy.
- Set time stopStop charging automatically after the specified number of minutes.
- Start charge for energyStart a charging session that will end after reaching the energy target.
- Start charge for timeStart a charging session that will end after the specified duration.
- Trigger firmware updateAsk the charger to search and install available firmware updates.
- Toggle OCPPEnable or disable the OCPP functionality.
- Set OCPP charge point IDConfigure the charge point identifier used in OCPP sessions.
- Set OCPP server addressConfigure the remote OCPP server URL.
- Set inverter IPConfigure the IP address of the linked inverter.
- Set installation voltageUpdate the installation voltage value via the local API.
- Scan Wi-Fi networksTrigger a Wi-Fi scan and emit the list of visible networks as an event.
- Create power profileStore a personalised power profile (v2).
- Update power profileUpdate an existing personalised power profile (v2).
- Get power profileRetrieve a personalised power profile using its timestamp.
Troubleshooting
- Repair noticesNotices it can show in Settings, Repairs:V2C Cloud is not authenticating — running on LAN only
From the README
This custom integration links Home Assistant with the V2C Cloud platform. It combines the public cloud API with the wallbox local HTTP interface so that real-time data and frequent controls use the LAN endpoint while configuration tasks still rely on the official cloud endpoints. It is purpose-built for the official V2C Cloud APIs and the local APIs exposed by V2C Trydan chargers.
- Guided onboarding – the config flow either asks for your API key and validates it against /pairings/me, or, (new in 1.4.0) sets up a charger from its LAN IP address alone, with no V2C account at all.
- API key management – the API key can be updated at any time via the Reconfigure button in the integration panel, without removing and re-adding the integration.
- Cloud + LAN hybrid – the integration polls every 30 seconds by default (configurable 5-300 s per integration via Reconfigure) for telemetry and rapid feedback, while the cloud API handles pairing…
- Runs through a V2C Cloud outage (new in 1.4.0) – on a Local (Wi-Fi) setup, a rejected API key or an unreachable cloud no longer takes the integration down: it keeps polling and controlling the…
- Per-charger manual IP (new in 1.4.0) – pin a fixed local address per charger from the integration options, for when the cloud can't currently supply one, or isn't configured at all.
Shows in Vulpo
Quick Toggle card, Button card, Select card, Chart card, Apple Watch, Control Center.Information
- Installs
- 103 sharing analytics
- GitHub stars
- 10
- Connection
- Uses the vendor's cloud
- Upkeep
- Updated in the last 6 months
- Version
- v1.4.0,
- Category
- Energy, EV charging
- Kind
- Marketplace integration
- Needs
- Needs the Marketplace (HACS on 2026.10 and older)
- Domain
v2c_cloud- Issues
- Report an issue












